Scan a directory for AI-generated code quality issues. Detects hallucinated imports, phantom packages, stale APIs, security anti-patterns, and more. Supports TypeScript, JavaScript, Python, Java, Go, and Kotlin.
AI agents call scan_directory to retrieve information from Open Code Review without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
scan_directory is a static analysis tool that examines code and reports findings. It retrieves and analyzes information about code quality but does not execute code, modify files, delete content, or move money. The blast radius of misuse is minimal—worst case, false positives in a security report. This is purely a Read operation.
From the tool's definition Tool performs scanning and analysis of code to detect issues without modifying, executing, or deleting any code. The description states it 'detects' and 'scans' for defects, which are read-only operations. No side effects or code modifications are mentioned.
Documented attack patterns abuse exactly the kind of access scan_directory gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Open Code Review, and nothing reaches the server without passing your rules. This is the rule we recommend for scan_directory:
{
"version": "1",
"default": "deny",
"tools": {
"scan_directory": {}
}
}scan_directory 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 a directory for AI-generated code quality issues. Detects hallucinated imports, phantom packages, stale APIs, security anti-patterns, and more. Supports TypeScript, JavaScript, Python, Java, Go, and Kotlin. It is categorised as a Read tool in the Open Code Review MCP Server, which means it retrieves data without modifying state.
Register the Open Code Review 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 Open Code Review. 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 Open Code Review MCP server (raye-deng/open-code-review). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Open Code Review, 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.
4 Open Code Review tools catalogued and risk-classified — across an index of 43,000+ MCP servers.