Scan a local MCP server directory for backdoors, exfiltration code, obfuscation, and dangerous patterns. Use this for MCP servers installed locally or cloned from GitHub.
AI agents call scan_directory to retrieve information from Mcp Shield without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is fundamentally a read operation—it inspects files and directories to detect security threats without modifying the target system. However, severity is high because the tool operates on sensitive code repositories where misconfiguration or a compromised scanner could expose secret keys, API tokens, or other sensitive data embedded in source code.
From the tool's definition The tool 'scan_directory' scans a local MCP server directory for security issues (backdoors, exfiltration code, obfuscation, dangerous patterns). It retrieves and analyzes files without modifying or deleting them.
Attacks that exploit this kind of access
Scan a local MCP server directory for backdoors, exfiltration code, obfuscation, and dangerous patterns. Use this for MCP servers installed locally or cloned from GitHub. It is categorised as a Read tool in the Mcp Shield MCP Server, which means it retrieves data without modifying state.
Register the Mcp Shield MCP server in PolicyLayer and add a rule for scan_directory: 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 Mcp Shield. Nothing to install.
scan_directory 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_directory 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_directory. 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_directory is provided by the Mcp Shield MCP server (muhannad-hash/mcp-shield). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →