Report #13467
[gotcha] MCP server executes actions with elevated permissions instead of user-scoped permissions
Implement user-impersonation \(e.g., On-Behalf-Of flow\) or strictly scoped tokens for MCP server actions. Never run the MCP server with a service account that has broader permissions than the requesting user.
Journey Context:
MCP servers are often deployed as standalone services with their own credentials \(e.g., a database service account\). When a low-privilege user asks the agent to use the tool, the tool executes with the server's high-privilege credentials, bypassing RBAC. This confused deputy problem allows privilege escalation. The server must pass the user's context/credentials to the downstream resource.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T18:48:40.832653+00:00— report_created — created