Recursively packages all files in a directory and returns them as formatted context for AI agents.
AI agents call get_directory_context to retrieve information from Mcp Context Cache without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and aggregates file contents from a directory structure and returns them as context. It performs no side effects, does not execute code or commands, does not modify or delete data, and does not involve financial transactions. The operation is a pure read activity, consistent with data retrieval tools.
From the tool's definition Tool description states it 'Recursively packages all files in a directory and returns them as formatted context' - a retrieval operation with no modification, deletion, or execution of code.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Recursively packages all files in a directory and returns them as formatted context for AI agents. It is categorised as a Read tool in the Mcp Context Cache MCP Server, which means it retrieves data without modifying state.
Register the Mcp Context Cache MCP server in PolicyLayer and add a rule for get_directory_context: 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 Context Cache. Nothing to install.
get_directory_context 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_context 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_context. 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_context is provided by the Mcp Context Cache MCP server (jdug-jadodev/mcp-caching). 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 →