Save or update a project context file. Use when user says
AI agents use save_context to create or update resources in Compass MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Compass MCP environment.
This tool writes or modifies project context files stored as local markdown, which is reversible (files can be edited or deleted). It does not delete data irreversibly, execute arbitrary code, or involve financial transactions.
From the tool's definition Tool name 'save_context' and description 'Save or update a project context file' indicate creation or modification of data.
Documented attack patterns abuse exactly the kind of access save_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 save_context:
{
"version": "1",
"default": "deny",
"tools": {
"save_context": {
"limits": [
{
"counter": "save_context_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}save_context stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Save or update a project context file. Use when user says. It is categorised as a Write tool in the Compass MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Compass MCP server in PolicyLayer and add a rule for save_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.
save_context is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the save_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 save_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.
save_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.