mcp tool safety schema gatekeeper

The problem

Deploying Model Context Protocol (MCP) tools with loose schemas or inadequate permission checks leads to prompt injection risks and catastrophic data loss. Developers often forget to implement explicit confirmations for destructive actions or fail to validate response shapes, causing integration breaks.

What it does

• Enforces strict JSON Schema validation for all tool parameters to prevent malformed payloads and denial-of-service attacks.
• Audits permission scopes to ensure tools follow the principle of least privilege and do not leak environment secrets.
• Mandates explicit user confirmation flows for destructive operations like database drops or file deletions.
• Verifies response shape consistency to ensure predictable output for downstream LLM consumption.
• Checks for naming collisions and ambiguous identifiers that confuse agentic reasoning.

Frameworks & tools

Model Context Protocol (MCP), JSON Schema, Node.js, Python, and TypeScript MCP SDKs.

Why this beats prompting it yourself

Writing a prompt to check safety often misses edge cases like additionalProperties: false or specific enum constraints. This skill provides a systematic, multi-point audit trail that mimics a professional security review, ensuring nothing is overlooked before production deployment.

Use cases

• Reviewing a new MCP server manifest before registering it with Claude or Cursor.
• Auditing destructive tools like 'delete_row' to ensure they require a manual confirmation flag.
• Refactoring legacy tool schemas to meet strict JSON Schema standards.
• Generating a safety compliance report for team lead approval before a production release.

Known limitations

Does not perform runtime traffic analysis or live penetration testing. Requires the developer to provide the tool definitions or source code for analysis.