Low Risk

memory_expand

Fetch memories by ID with surrounding timeline context.

How to control memory_expand ↓

What memory_expand does on Codemem

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

Low Risk

Why memory_expand needs a policy

This tool retrieves stored memory records and contextual information by ID. It has no side effects—it does not create, modify, delete, or execute any operations. The retrieval of coding session context and memories is purely informational and reversible. Confidence is high because the description clearly indicates a fetch/query operation.

From the tool's definition Tool name 'memory_expand' and description 'Fetch memories by ID with surrounding timeline context' indicate a retrieval operation. The verb 'Fetch' is a read action that queries existing data without modification.

Documented attack patterns abuse exactly the kind of access memory_expand gives an agent:

How to control memory_expand

PolicyLayer is an MCP gateway — it sits between your AI agents and Codemem, and nothing reaches the server without passing your rules. This is the rule we recommend for memory_expand:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "memory_expand": {}
  }
}

memory_expand is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Codemem — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about memory_expand

What does the memory_expand tool do? +

Fetch memories by ID with surrounding timeline context. It is categorised as a Read tool in the Codemem MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on memory_expand? +

Register the Codemem MCP server in PolicyLayer and add a rule for memory_expand: 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 Codemem. Nothing to install.

What risk level is memory_expand? +

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

Can I rate-limit memory_expand? +

Yes. Add a rate_limit block to the memory_expand 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_expand completely? +

Set action: deny in the PolicyLayer policy for memory_expand. 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_expand? +

memory_expand is provided by the Codemem MCP server (kunickiaj/codemem). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Codemem tool call.

Start from Codemem, 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.

13 Codemem tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.