Notifications
Clear all
Topic starter
25/08/2026 9:13 am
TL;DR: AI agents, MCP servers, and delegated tool access are creating a runtime identity problem that traditional automation controls were built to assume away, according to Britive. The core shift is that access must be verified, constrained, observed, and revoked continuously because agent behaviour can change mid-task and invalidate standing-access assumptions.
NHIMG editorial — based on content published by Britive: Securing AI Agents Beyond the MCP Gateway
By the numbers:
- When AWS credentials are exposed publicly, attackers attempt access within an average of 17 minutes and as quickly as 9 minutes in some cases.
- While 71% of IT teams have been advised on AI agent data access, only 47% of compliance teams, 39% of legal teams, and 34% of executives have the same visibility.
Questions worth separating out
Q: How should security teams govern AI agents that can choose tools at runtime?
A: Security teams should govern runtime agent choice as an access event, not as a simple application action.
Q: Why do AI agents complicate least-privilege access models?
A: Because agents often use shared or long-lived NHIs, move quickly, and cross platform boundaries that human-centric review processes do not cover well.
Q: What breaks when agent access is treated like a normal service account?
A: You lose visibility into why a specific call was allowed, which context justified it, and whether the action still made sense at the time it executed.
Practitioner guidance
- Assign each agent a unique identity and named owner Stop using borrowed human logins or shared service identities for agent activity.
- Broker tool access through a single runtime policy point Centralise allowed MCP servers, tool filtering, and token custody so the agent never holds reusable secrets directly.
- Issue privilege only for the current task Use ephemeral credentials or ephemeral accounts that are created at authorization time and removed as soon as the task completes or conditions change.
What's in the full article
Britive's full article covers the operational detail this post intentionally leaves for the source:
- How Britive models AI agents as first-class identities with owners, business purpose, and access profiles.
- How the ARC flow maps verify, assess, authorize, observe, and revoke stages to live agent activity.
- How the MCP gateway handles token custody, tool filtering, command blocking, and audit logging.
- How ephemeral credentials and temporary accounts are issued and removed for database and API access.
👉 Read Britive's analysis of securing AI agents beyond the MCP gateway →
AI agent identity beyond MCP gateways: are your controls keeping up?
Explore further
25/08/2026 9:14 am
Runtime authorisation is now the governing concept for AI agents. Traditional identity programmes were built to decide access before execution, then rely on logs and reviews after the fact. AI agents collapse that sequence because the meaningful decision happens while the task is in flight. That means the field has moved from provisioning-first governance to runtime governance, and practitioners should treat continuous authorisation as the new baseline for agentic access.
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 AI Agents: The New Attack Surface report.
- 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, according to SailPoint.
A question worth separating out:
Q: Who is accountable when an AI agent takes an unsafe action?
A: Accountability should sit with the business owner of the agent, the team that provisioned the access, and the control owners responsible for monitoring and revocation. If no one can answer who approved the identity, the scope, and the oversight model, the governance framework is not complete enough for production.
👉 Read our full editorial: Securing AI agent identity beyond the MCP gateway
