Saves a new memory, decision, or insight from the current session.
AI agents use cortex_save_memory to create or update resources in Cortex Memory — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cortex Memory environment.
This tool creates and stores new data (memories, decisions, insights) in the cortex system, making it a Write operation. Severity is medium because misuse could pollute project memory with incorrect information, misleading future sessions, but the effects are reversible (memories can be corrected or deleted). The confidence is high because the description clearly indicates data creation/storage.
From the tool's definition Tool name is 'cortex_save_memory' and description states it 'Saves a new memory, decision, or insight from the current session' — this is a create/write operation that modifies persistent project state.
Documented attack patterns abuse exactly the kind of access cortex_save_memory gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Cortex Memory, and nothing reaches the server without passing your rules. This is the rule we recommend for cortex_save_memory:
{
"version": "1",
"default": "deny",
"tools": {
"cortex_save_memory": {
"limits": [
{
"counter": "cortex_save_memory_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}cortex_save_memory 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.
Saves a new memory, decision, or insight from the current session. It is categorised as a Write tool in the Cortex Memory MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Cortex Memory MCP server in PolicyLayer and add a rule for cortex_save_memory: 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 Cortex Memory. Nothing to install.
cortex_save_memory 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 cortex_save_memory 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 cortex_save_memory. 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.
cortex_save_memory is provided by the Cortex Memory MCP server (skullfire07/cortex-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Cortex Memory, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 Cortex Memory tools catalogued and risk-classified — across an index of 43,000+ MCP servers.