Scan directory - file tree with one-line gists per file, code health and churn labels (cheap overview, good first call). Replaces Glob/ls for ALL file types
AI agents call scan_directory to retrieve information from Scantool - File Scanner MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
scan_directory performs passive analysis and retrieval of directory structure and file metadata using tree-sitter parsing. It reads source code to extract classes, functions, and line numbers but does not create, modify, delete, or execute any code. This is a Read operation with minimal risk—it enables codebase exploration without side effects.
From the tool's definition Tool provides file tree overview with code analysis and metadata extraction. Descriptions across the server emphasize 'extracting', 'analyzing', 'scanning', and 'exploring' without any modification, deletion, or execution capabilities.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Scan directory - file tree with one-line gists per file, code health and churn labels (cheap overview, good first call). Replaces Glob/ls for ALL file types. It is categorised as a Read tool in the Scantool - File Scanner MCP MCP Server, which means it retrieves data without modifying state.
Register the Scantool - File Scanner 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 Scantool - File Scanner MCP. 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 Scantool - File Scanner MCP server (mariusei/file-scanner-mcp). 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 →