Scan an MCP server for security vulnerabilities, description quality,
AI agents call scan_mcp_server to retrieve information from Teeshield without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs static analysis (scanning) of MCP server tool definitions, which is fundamentally a read/inspect operation. It retrieves and analyzes tool definitions without modifying them. Severity is medium because the tool inspects potentially sensitive server configurations and tool descriptions, and could expose security-relevant information about MCP server internals.
From the tool's definition 'Scan an MCP server for security vulnerabilities, description quality' — scanning/reading tool definitions for analysis
Documented attack patterns abuse exactly the kind of access scan_mcp_server gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Teeshield, and nothing reaches the server without passing your rules. This is the rule we recommend for scan_mcp_server:
{
"version": "1",
"default": "deny",
"tools": {
"scan_mcp_server": {}
}
} scan_mcp_server is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Scan an MCP server for security vulnerabilities, description quality,. It is categorised as a Read tool in the Teeshield MCP Server, which means it retrieves data without modifying state.
Register the Teeshield MCP server in PolicyLayer and add a rule for scan_mcp_server: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Teeshield. Nothing to install.
scan_mcp_server is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the scan_mcp_server rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for scan_mcp_server. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
scan_mcp_server is provided by the Teeshield MCP server (teehooai/spidershield). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Teeshield, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
3 Teeshield tools catalogued and risk-classified — across an index of 43,000+ MCP servers.