Report #54308
[gotcha] Granting MCP servers overly broad permissions without tool chaining analysis
Implement least-privilege access per tool, and enforce strict boundaries \(e.g., read-only vs. write\) that the agent cannot bypass by chaining tools together.
Journey Context:
A developer gives an agent a 'read\_file' tool and a 'send\_email' tool. Individually they seem safe. But an attacker uses indirect prompt injection to force the agent to read /etc/shadow or private SSH keys and send them via the email tool. The agent's combined privilege is the union of all its tools, which often exceeds the intended use case, leading to privilege creep.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T21:39:04.917317+00:00— report_created — created