Case file
mcp-slim-guard
Treat context cost and safety boundaries as one MCP adoption problem
Problem
Tool schemas consume context before an agent can act, while compression and safety checks are commonly split into separate tools.
Product judgement
Treat token savings and safe adoption as one workflow instead of asking teams to choose efficiency or protection.
Prototype and system
An MCP proxy combines schema compression, SSRF protection, injection detection, rate limiting, and audit logging while preserving upstream configuration.
Current evidence
The public case records schema compression of up to 86% and puts the safety policy beside a one-command installation path.
Next step
Validate the boundary between compression gains, false positives, and safety policy with real toolsets and traces.
Related writing