Notifications
Clear all
Topic starter
22/07/2026 4:35 pm
TL;DR: AI agent security solutions now split between tools that protect agents and tools that use agents, but the core risk remains the same: 97% of breached organisations with an AI-related security incident lacked proper AI access controls, according to Apono. The real issue is privilege, runtime enforcement, and auditability, not prompt filtering alone.
NHIMG editorial — based on content published by Apono: Top 16 AI Agent Security Solutions
By the numbers:
- 97% of breached organizations that experienced an AI-related security incident lacked proper AI access controls.
- 63% of organizations had no AI governance policies in place to manage AI or prevent shadow AI.
- 53% of MCP servers expose credentials through hard-coded values in configuration files.
Questions worth separating out
Q: How should security teams govern AI agents that can access enterprise systems?
A: Security teams should govern AI agents as non-human identities with explicit ownership, scoped privileges, and continuous monitoring.
Q: Why do agentic AI systems create more security risk than standard chatbots?
A: Agentic systems can turn model output into action, which means a bad instruction can affect code flow, tool use, and downstream state.
Q: What do security teams get wrong about governing AI agents?
A: They often treat agents like another automation layer instead of governed non-human actors with their own access paths.
Practitioner guidance
- Map every agent to a named owner and business purpose Do not allow anonymous agent identities, shared tokens, or unclear accountability.
- Replace standing agent access with task-scoped permissions Issue ephemeral credentials for the specific task, then revoke them immediately after execution.
- Separate MCP tool review from general application review Inspect MCP servers for hard-coded secrets, excessive tool permissions, and unscoped client trust.
What's in the full article
Apono's full article covers the operational detail this post intentionally leaves for the source:
- Side-by-side breakdown of the 16 tools and the specific AI security problem each one addresses
- Product-level capability notes for discovery, runtime enforcement, red teaming, and auditability
- Category-by-category comparison of tools that secure agents versus tools that use agents
- Practical positioning guidance for teams choosing between access control, prompt protection, and SOC automation
👉 Read Apono's roundup of 16 AI agent security solutions →
AI agent security tools: are your access controls keeping up?
Explore further
22/07/2026 4:41 pm
AI agent security is now an identity governance problem, not just a model safety problem. The article makes clear that the meaningful controls are privilege scope, runtime enforcement, auditability, and ownership. That is the same control stack identity teams already use for non-human identities, but now applied to systems that can act at runtime. Practitioners should stop treating agents as a special case and govern them as high-risk identities.
A few things that frame the scale:
- Only 18% of MCP server deployments implement any form of access scoping for tool permissions, according to The State of MCP Server Security 2025.
- 53% of MCP servers expose credentials through hard-coded values in configuration files, according to The State of MCP Server Security 2025.
A question worth separating out:
Q: Who should be accountable for AI agent actions in enterprise systems?
A: Accountability should sit with the team that owns the agent, its policies, and the connected tools, not only with the person who typed the original prompt. When a software actor can send messages, update records, and move data across systems, responsibility must follow the governed identity and its enforcement layer.
👉 Read our full editorial: AI agent security is becoming an access control problem
