Review an MCP configuration for filesystem exposure, shell execution, credential access, internal networking and other high-impact permissions.
The checker looks for broad filesystem paths, shell execution, credential-like environment variables, internal-network targets, Docker socket access and other configuration signals that may grant an MCP server powerful access.
It performs static analysis only and does not execute the configured server.
Analyze MCP server configurations for filesystem, shell, credential, network and elevated-permission risks.
Use MCP Permission Checker 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.