Returns formatted context for a list of files. Use this to load specific files into AI agent context with caching.
AI agents call get_project_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 delivers file context data without creating, modifying, executing, or deleting anything. It is a caching and retrieval mechanism for project files. The security validation mentioned in the server description is a protective measure, not an indication of dangerous capability.
From the tool's definition Tool description states it 'Returns formatted context for a list of files' and is designed to 'load specific files into AI agent context with caching.' The verb 'Returns' and the function of retrieving/loading file content indicates a read-only operation with…
Attacks that exploit this kind of access
Returns formatted context for a list of files. Use this to load specific files into AI agent context with caching. 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_project_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_project_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_project_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_project_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_project_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.
get_project_context is one line of Mcp Context Cache's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →