memory_diff

See what changed since a timestamp — new, updated, and archived memories.

Server Exocortex shawnhack/exocortex
Category Read
Risk class Low
Parameters 00 required

What memory_diff does on Exocortex

AI agents call memory_diff to retrieve information from Exocortex without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why memory_diff needs a policy

memory_diff is a read-only operation that queries memory changelog/history to show new, updated, and archived entries. It has no side effects, does not create, modify, or delete data, and does not execute external operations. It simply surfaces metadata about what changed, making it a Read category tool with low severity.

From the tool's definition Tool description states 'See what changed since a timestamp' — a query operation that retrieves and displays changes to memories without modifying, deleting, or executing anything. The verb 'see' indicates passive data retrieval.

Questions about memory_diff

What does the memory_diff tool do? +

See what changed since a timestamp — new, updated, and archived memories. It is categorised as a Read tool in the Exocortex MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on memory_diff? +

Register the Exocortex MCP server in PolicyLayer and add a rule for memory_diff: 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.

What risk level is memory_diff? +

memory_diff is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit memory_diff? +

Yes. Add a rate_limit block to the memory_diff 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.

How do I block memory_diff completely? +

Set action: deny in the PolicyLayer policy for memory_diff. 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.

What MCP server provides memory_diff? +

memory_diff 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.