Topic starter
15/05/2026 7:41 pm
TL;DR: AI agent security depends on the harness, tools, and environment, not model behaviour alone, according to Backslash Security. That makes governance a lifecycle problem for agent permissions, tool drift, and runtime context.
Editorial analysis by NHI Mgmt Group, based on content published by Backslash Security: “Anthropic's Shared Responsibility Security Model for AI Agents, Explained”.
By the numbers:
- Anthropic reports that 93% of permission prompts were approved without reading.
- Anthropic says the clarification rate on complex tasks was just 16.4%.
Key questions
Q: Why do AI agents need centralized governance when they access multiple tools and models?
A: AI agents increase risk because they can invoke tools, move across systems, and act without direct human supervision.
Q: What are the signs that an AI agent permission model is failing in practice?
A: Common signs include agents requesting access beyond their role, attempting sensitive actions without clear approval, or operating with no audit trail for who approved what.
Q: What breaks when AI governance relies only on approval workflows?
A: Approval-only governance breaks when usage shifts outside sanctioned channels.
Practitioner guidance
- Map agents to the four responsibility layers Document which risks belong to the model provider and which belong to your organisation across harness, tools, and environment.
- Move approval logic out of the action path Design policy at harness level so the agent is authorised by rules and boundaries before execution begins, rather than waiting for a human to review each prompt or tool call.
- Inventory and revalidate connected tools Track every MCP server, API, and plugin an agent can use, then review any tool change as a governance event because post-approval drift changes the effective permission set.
Bottom line: AI agent security is not solved by model behaviour alone because the harness, tools, and environment carry most of the operational risk.
Glossary terms: AI Agent Shared Responsibility Model, Harness, Tool Drift, Persistent Memory Poisoning
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 18 hours ago by NHI Mgmt Group
15/05/2026 7:42 pm
Agent governance is a shared responsibility problem, not a model-safety problem. Anthropic’s four-layer framing is useful because it separates what the model provider can control from what the deploying organisation must own. The critical insight is that most security failure modes emerge in the harness, tools, and environment layers after the model decision is made. Practitioners should stop treating the model as the boundary of accountability.
A few things that frame the scale:
- 53% of security leaders expect AI to run major portions of their infrastructure autonomously within the next three years, according to the 2026 Infrastructure Identity Survey.
- 69% of security leaders agree identity management must fundamentally shift to address agentic AI systems, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: How should teams decide between model safety controls and agent governance controls?
A: Use model safety controls for the behaviour the model provider owns, but use agent governance controls for everything that happens after the model is connected to tools and data. The practical boundary is simple: if the risk comes from instructions, tool access, memory, or environment, the deploying organisation owns it and should govern it accordingly.
👉 Read our full editorial: Anthropic's shared responsibility model reframes AI agent governance