memory_session_end · Claude Memory MCP: Risk & Policy

WHAT IT DOES

What memory_session_end does on Claude Memory MCP

AI agents use memory_session_end to create or update resources in Claude Memory MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Memory MCP environment.

WHY IT NEEDS A POLICY

Why memory_session_end needs a policy

The tool creates and stores a session summary, which is a reversible write operation. It does not delete data (would be Destructive), execute arbitrary code (Execute), move funds (Financial), or retrieve data without modification (Read).

From the tool's definition Tool description explicitly states 'store its summary,' indicating it creates/writes a persistent record of session data to the memory system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

memory_session_end Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "memory_session_end": {
      "limits": [
        {
          "counter": "memory_session_end_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Claude Memory MCP, so you can run agents against it safely.

FAQ

Questions about memory_session_end

What does the memory_session_end tool do? +

End a session and store its summary. It is categorised as a Write tool in the Claude Memory MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on memory_session_end? +

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

What risk level is memory_session_end? +

memory_session_end is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit memory_session_end? +

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

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

memory_session_end is provided by the Claude Memory MCP server (navid-kianfar/claude-memory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.