mcp tool safety schema gatekeeper

    1

    Production-grade safety and schema auditor for Model Context Protocol (MCP) tool definitions.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    mcp tool safety schema gatekeeper

    Example session with this skill installed

    Review this MCP tool: delete_record(id: string, force: boolean). It deletes a row from the production DB without confirmation if force is true. Response is just a string.

    • Read your context and instructions
    • Compiled the mcp tool safety

    STATUS: BLOCKED

    Findings

    • Destructive Actions: FAIL. Must require a typed confirmation_text like "delete-production-db" instead of a simple boolean.
    • Response Shapes: FAIL. Returns plain string; must use a standard JSON envelope.
    • Validation: FAIL. Missing minLength for id.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    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.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Agents & Orchestration.

    Requires manual provision of tool schemas or source code. Does not perform live network or runtime security monitoring.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 3 months ago

    Permissions

    No special permissions declared or detected

    Listed3 months ago

    What's inside

    Frequently Asked Questions

    This tool audits your MCP server definitions against rigorous security standards, identifying prompt injection vulnerabilities, over-privileged permissions, and missing confirmation gates for destructive actions before you deploy.

    It is compatible with any agent or IDE that supports the Model Context Protocol, including Claude Desktop and Cursor, as well as MCP implementations in Node.js, Python, and TypeScript.

    No, this skill focuses on static analysis of your tool definitions and schemas; it does not monitor live traffic or require access to your production data to perform its safety audit.

    You will receive the core logic for the safety auditor, integration instructions for major MCP SDKs, and a suite of pre-defined JSON Schema templates to help you standardize your tool definitions.

    Prompting an AI to 'be safe' is unreliable; this skill uses a systematic, multi-point audit that enforces strict JSON Schema constraints (like 'additionalProperties: false') that LLMs often overlook during manual reviews.

    Yes, the gatekeeper is designed to be integrated into CI/CD pipelines to ensure every new tool or schema update passes safety compliance before being registered with your agent.

    New in Agents & Orchestration