Correct a memory that contains wrong or outdated information. Creates a new memory with the corrected content, supersedes the old one, and links them. Use when a fact, decision, or technique has changed and the old memory would mislead future retrieval.
AI agents use memory_correct to create or update resources in Exocortex — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Exocortex environment.
The tool modifies the memory store by creating a new memory and marking the old one as superseded. While it alters existing data, the old memory is linked rather than deleted, making this reversible in principle. The primary action is a write/update operation. Misuse could corrupt the agent's persistent memory with false information, warranting medium severity.
From the tool's definition Creates a new memory with the corrected content, supersedes the old one, and links them
Attacks that exploit this kind of access
Correct a memory that contains wrong or outdated information. Creates a new memory with the corrected content, supersedes the old one, and links them. Use when a fact, decision, or technique has changed and the old memory would mislead future retrieval. It is categorised as a Write tool in the Exocortex MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Exocortex MCP server in PolicyLayer and add a rule for memory_correct: 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 Exocortex. Nothing to install.
memory_correct 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 memory_correct 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 memory_correct. 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.
memory_correct is provided by the Exocortex MCP server (shawnhack/exocortex). 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 →