Get the complete directory structure with file metadata
AI agents call get_directory_structure to retrieve information from Enhanced Directory Context MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns directory metadata without creating, modifying, deleting, or executing any operations. It is purely informational and read-only, consistent with the Read category definition (retrieves or queries data; no side effects).
From the tool's definition Tool name 'get_directory_structure' and description 'Get the complete directory structure with file metadata' indicate a retrieval operation with no modifications or side effects.
Attacks that exploit this kind of access
Get the complete directory structure with file metadata. It is categorised as a Read tool in the Enhanced Directory Context MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Enhanced Directory Context MCP Server MCP server in PolicyLayer and add a rule for get_directory_structure: 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 Enhanced Directory Context MCP Server. Nothing to install.
get_directory_structure 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 get_directory_structure 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 get_directory_structure. 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.
get_directory_structure is provided by the Enhanced Directory Context MCP Server MCP server (pwalagov/file-control-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 →