Paste MCP tool definitions to identify potentially dangerous capabilities and review read-only, destructive, open-world and idempotency annotations.
The scanner reviews tool names, descriptions and security-relevant annotations. It highlights command execution, destructive actions, writes, network access, credential access, communications and financial operations.
Risk scores are heuristic and should support manual review rather than replace it.
Analyze MCP tool definitions and annotations for command execution, destructive operations, writes, networking, credentials and other high-impact capabilities.
Use MCP Tool Risk Scanner as a focused pre-flight utility while building, reviewing or debugging an MCP integration. Paste the relevant configuration, protocol message, metadata, schema or value into the tool and review the returned findings before the same data reaches a production client or server.
Use the findings as a pre-deployment security review rather than as proof that an MCP server is safe. Security depends on runtime isolation, authorization, deployment policy and the behavior of the connected tools and systems.
A clean result means the input passed the rules implemented by this utility. It does not guarantee application security, protocol interoperability or correct business behavior. Test important integrations against the exact MCP client, SDK, gateway and server versions used in your deployment.