Report #12476
[gotcha] Sensitive data leaks into context via MCP tool descriptions and examples
Audit tool names, descriptions, and schema examples. Never use real URLs, internal hostnames, or actual API patterns in the schema; use generic placeholders like 'example.com' or 'your-instance.atlassian.net'.
Journey Context:
To help the LLM use the tool correctly, developers put realistic examples in the tool description \(e.g., 'Use server prod-db-01.internal'\). The LLM memorizes this and injects it into outputs, or the schema itself gets logged in the agent's context history, leaking internal infrastructure details to the user or third-party LLM provider.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T16:10:34.077805+00:00— report_created — created