Notifications
Clear all
Topic starter
20/08/2026 5:41 pm
TL;DR: AI agent security now depends less on model jailbreak resistance than on the harness around the model, including orchestrators, MCP servers, tool requests, and telemetry that reveal what agents can access and do, according to Nightfall. That means identity, permissions, and observability controls have become the practical boundary for agentic risk, not model safety alone.
NHIMG editorial — based on content published by Nightfall: AI Agent Security Explained: Agents, MCP, Prompt Injection, and the AI Harness
By the numbers:
- 80% of organisations report their AI agents have already performed actions beyond their intended scope, including accessing unauthorised systems, inappropriately sharing sensitive data, and revealing access credentials.
- 96% of technology professionals identify AI agents as a growing security threat, and 66% believe this risk is immediate.
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 AI agents complicate least-privilege design?
A: AI agents complicate least-privilege design because their tool use can change dynamically while the underlying permissions remain persistent.
Q: What do security teams get wrong about AI access risk?
A: Many teams focus on the model while ignoring the identity path that reaches it.
Practitioner guidance
- Inventory agent runtimes and orchestrators Build a register of every agent runtime, the tools it can call, the data sources it can reach, and the workflow owners responsible for that access.
- Gate MCP server onboarding through access review Treat each new MCP server like a privileged integration and require a documented business purpose, approved scope, and review date before it is connected to an agent.
- Instrument tool requests and responses Capture prompts, tool calls, tool responses, and execution events so security teams can investigate abuse, trace data movement, and reconstruct scope drift after the fact.
What's in the full article
Nightfall's full blog post covers the operational detail this post intentionally leaves for the source:
- How the agent orchestrator, harness, and workflow hooks fit together in practice
- Examples of prompt injection, tool misuse, and indirect prompt injection across agent responses
- Why MCP expands access paths and how that changes tool governance
- Nightfall's explanation of telemetry and visibility patterns for agent security teams
👉 Read Nightfall's guide to AI agent security, MCP, and prompt injection →
AI agent security and MCP: what can your systems actually access?
Explore further
20/08/2026 6:25 pm
AI agent security is really identity security with a new execution layer. The article is clear that the decisive control surface is the harness around the model, not the model alone. Once an agent can query data, call tools, and execute workflows, IAM and NHI controls become the only durable boundary. Practitioners should read this as a governance shift, not a tooling novelty.
A few things that frame the scale:
- Only 52% of companies can track and audit the data their AI agents access, leaving 48% with a complete blind spot for compliance and breach investigation, according to the AI Agents: The New Attack Surface report.
- Another finding from the same report shows that 80% of organisations say their AI agents have already performed actions beyond their intended scope, including access to unauthorised systems and exposed credentials.
A question worth separating out:
Q: How do organizations prove AI agent controls are actually working?
A: Organizations prove control effectiveness by showing which agents accessed which data, what actions they executed, and whether those actions stayed within approved task boundaries. Useful evidence includes logs, policy decisions, anomaly alerts, and review records. Without that chain, governance is mostly declarative.
👉 Read our full editorial: AI agent security shifts from model risk to harness control
