Scan a directory and get stats about files (photos, CAD, documents, code). Use this to preview before batch ingesting.
AI agents call scan_directory to retrieve information from ChromaDB Local MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only scan of a directory to gather statistics and information about files. It has no side effects—it does not create, modify, delete, or execute anything. It is purely informational, used to preview directory contents before potential batch operations. The low severity reflects the minimal blast radius: an agent misusing this could only view filesystem metadata, not alter or act upon data.
From the tool's definition scan_directory: 'Scan a directory and get stats about files...Use this to preview before batch ingesting.' The tool retrieves file statistics and metadata without modifying, deleting, or executing any data.
Attacks that exploit this kind of access
Scan a directory and get stats about files (photos, CAD, documents, code). Use this to preview before batch ingesting. It is categorised as a Read tool in the ChromaDB Local MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ChromaDB Local MCP Server 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 ChromaDB Local MCP Server. 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 ChromaDB Local MCP Server MCP server (vespo92/chromadblocal-mcp-server). 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 →