Read a project context file. Use when user references a project —
AI agents call get_context to retrieve information from Compass MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads project context from local markdown files. It has no side effects, does not modify data, execute code, or delete anything. It is a simple retrieval operation that enables knowledge sharing across sessions.
From the tool's definition Tool name is 'get_context' and description states 'Read a project context file' — retrieves data without modification.
Documented attack patterns abuse exactly the kind of access get_context gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Compass MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_context:
{
"version": "1",
"default": "deny",
"tools": {
"get_context": {}
}
}get_context is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Read a project context file. Use when user references a project —. It is categorised as a Read tool in the Compass MCP MCP Server, which means it retrieves data without modifying state.
Register the Compass MCP server in PolicyLayer and add a rule for get_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 Compass MCP. Nothing to install.
get_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_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_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_context is provided by the Compass MCP server (richlira/compass-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 Compass MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
6 Compass MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.