Report #69875
[gotcha] Monolithic MCP servers with overly broad permissions lead to catastrophic blast radius upon compromise
Build minimal, scoped MCP servers \(e.g., one for reading a specific directory, one for a specific API\) and enforce the principle of least privilege; run servers in isolated containers/sandboxes.
Journey Context:
To save time, developers often expose entire filesystems or broad API scopes to a single MCP server. If an attacker performs tool poisoning or prompt injection on one tool, they inherit the permissions of the entire server. Micro-segmenting tools into different servers with distinct permissions limits the blast radius of a compromised tool.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T23:46:07.230036+00:00— report_created — created