Access Control and Permissions

What an agent can reach, with which credentials, on whose authority.

The MCP specification released July 28, 2026 deprecates dynamic client registration and requires issuer validation, after a run of MCP access failures in 2025. The largest, the mcp-remote flaw CVE-2025-6514, scored 9.6 of 10 in a package downloaded more than 437,000 times.

Agent access failures and fixes: May 2025 GitHub MCP leak; Jun 2025 Asana MCP exposure; Jul 2025 mcp-remote CVSS 9.6; Dec 2025 OWASP agentic top 10; Apr 2026 PocketOS deletion; Jun 2026 MCP enterprise authorization; Jul 2026 MCP spec 2026-07-28 AGENT ACCESS FAILURES AND FIXES MAY 2025GitHub MCPleak JUN 2025Asana MCPexposure JUL 2025mcp-remoteCVSS 9.6 DEC 2025OWASP agentictop 10 APR 2026PocketOSdeletion JUN 2026MCP enterpriseauthorization JUL 2026MCP spec2026-07-28 FailureFix or standard
mcp-remote CVSS score
9.6
Asana MCP customers exposed
~1,000
OWASP agentic risks
10
Registry failures
7

Registry

Seven failed access controls across five registry incidents

Each row is a control that was in place, or should have been, and did not hold. The incident record explains who was responsible and what changed afterward.

Registry incidents where access and authorization failed
IncidentDateControlResponsibleWhat failed
EchoLeak Turns Microsoft 365 Copilot Into a Data LeakJan 2025Content security allowlistMicrosoftAn allowed Teams preview service fetched the attacker's address
Replit Agent Deletes the SaaStr DatabaseJul 2025Environment separationReplitApps used one database for development and live data
Stolen Drift Tokens Drain Salesforce DataAug 2025Connected-app scopeCustomersDrift's tokens allowed broad bulk queries
Stolen Drift Tokens Drain Salesforce DataAug 2025Secrets in recordsCustomersCredentials stored in CRM records let attackers reach further systems
Nx Malware Turns AI Coding Tools Against Their UsersAug 2025Permission prompts in AI toolsUsers and tool makersCommand-line flags skipped every approval prompt
Cursor Agent Deletes the PocketOS DatabaseApr 2026Least-privilege tokenPocketOS and RailwayA full-permission token let a staging task delete production
Cursor Agent Deletes the PocketOS DatabaseApr 2026Delayed deleteRailwayAn old endpoint deleted at once with no delay

Implementations

Agent access is moving from stored keys to short-lived, centrally managed tokens

MCP's Enterprise-Managed Authorization lets an organization approve MCP servers centrally with single sign-on. Microsoft's Agent 365 attaches access policy to each agent's directory identity. GitHub's coding agent runs behind a default outbound firewall, though GitHub says MCP servers are outside it. China's TC260 draft guide covers agents from installation to removal, including unsanctioned "shadow" agents.

Named access and authorization implementations
ImplementationVendor or bodyCountryWhat it enforcesStatus
Agent 365 with Entra Agent IDMicrosoftUnited StatesPer-agent identity and access policy across the agent registryGA May 1, 2026
Copilot coding agent firewallGitHubUnited StatesDefault-on outbound allowlist for the agent shell; MCP servers not coveredCurrent
MCP Enterprise-Managed AuthorizationMCP project and OktaUnited StatesCentral authorization of MCP servers with single sign-onStable Jun 18, 2026
MCP specification 2026-07-28MCP project (Agentic AI Foundation)InternationalDeprecates dynamic client registration; issuer validation; credentials bound to issuerReleased Jul 28, 2026
MCP-scan and Invariant GuardrailsInvariant LabsSwitzerlandAudits agent-to-MCP traffic; per-session repository limitsMay 2025
Practice guide for OpenClaw-class agentsTC260ChinaInstall-to-removal lifecycle controls; governance of shadow agentsDraft Apr 2026

Row color shows the agent class served: orange physical, teal personal and ambient, blue software.

Recent events

  • On May 26, 2025 Invariant Labs showed a public GitHub issue steering an agent into leaking private repository data through the GitHub MCP server.
  • A flaw in Asana's MCP server exposed data across about 1,000 customer organizations for over a month before it was found on June 4, 2025.
  • JFrog found remote code execution in mcp-remote versions 0.0.5 to 0.1.15; version 0.1.16 fixed it on June 17, 2025.
  • A Cursor agent used a broad Railway token to delete the PocketOS production database in April 2026.

Exposure

Integrations and permissions rates very significant or critical for six of 17 agent types

The access and authorization discipline covers the integrations and permissions dimension of the agent attack surface ratings. These agent types depend on it most.

Agent types most exposed on this dimension
Agent typeDimensionRatingWhy
Workflow agentsIntegrations and permissionsCriticalThe defining dimension
Enterprise agentsIntegrations and permissionsCriticalConnectors and MCP servers set what an agent can reach
Phones and tabletsIntegrations and permissionsVery significantApp integration, third-party AI routing (such as Apple Intelligence to ChatGPT), enterprise integrations, cloud sync
Smart home assistantsIntegrations and permissionsVery significantCross-vendor integration through Matter and major platforms
Coding and research agentsIntegrations and permissionsVery significantThe defining dimension for this category
Commerce agentsIntegrations and permissionsVery significantThe defining dimension

Rules

Open specifications and OWASP set agent access practice; China's rules add approval duties

Rules and standards for access and authorization
RuleJurisdictionWhat it requiresStatus
MCP specification 2026-07-28Open standardClient ID metadata documents replace dynamic registration; issuer validation; credentials bound to issuerReleased Jul 28, 2026
OWASP Top 10 for Agentic ApplicationsInternationalIdentity and privilege abuse, tool misuse and insecure agent-to-agent trafficDec 2025
CoSAI Agentic Identity and Access ManagementIndustry (OASIS)Agents as non-human identities with full lifecycle managementMar 2026
China agent Implementation OpinionsChinaDefined decision authority; human approval for significant actionsEffective Jul 15, 2026
CNCERT OpenClaw security guidelineChinaNo admin privileges; isolated hostsMar 2026

Status colors: green in force, blue voluntary standard or framework, amber adopted and phasing in, gray draft or pending, red withdrawn.

Limits

Least privilege is hard to hold when agents need broad access to be useful

Permissions also tend to grow over time, and access control also cannot tell a legitimate instruction from an injected one once the agent is allowed to act.

Record

Page Record

Datasets
ai_control_implementations.csv (6 rows for this page); ai_incident_controls.csv (7 linked); ai_attack_surface.csv
Key sources
GitHub
Invariant Labs
MCP project (Agentic AI Foundation)
MCP project and Okta
Microsoft
TC260
Source notes
MCP-scan and Invariant Guardrails: vendor source; Practice guide for OpenClaw-class agents: secondary source
Last verified
October 2026