session_end

RARELY NEEDED — Stop/SessionEnd hooks handle teardown automatically. Just a summary recap; memories save without it.

SERVERClaude Engram SOURCE20alexl/claude-engram

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/20alexl-claude-engram/session-end.md

WHAT IT DOES

What session_end does on Claude Engram

AI agents call session_end to retrieve information from Claude Engram without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why session_end is rated Low

The tool is described as providing a summary recap at session end, with the actual memory persistence handled automatically elsewhere. It has no independent side effects and is rarely needed. This makes it primarily a Read/informational operation. Severity is low because misuse has minimal blast radius.

From the tool's definition 'Just a summary recap; memories save without it' — the tool produces a summary but does not create/modify/delete data itself; teardown and memory saving are handled automatically by hooks

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs session_end safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Engram, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For session_end, this is the rule to start with:

session_end Allowed

session_end is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "session_end": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Claude Engram, apply this rule, and every session_end call is checked against it from then on.

FAQ

Questions about session_end

What does the session_end tool do? +

RARELY NEEDED — Stop/SessionEnd hooks handle teardown automatically. Just a summary recap; memories save without it. It is categorised as a Read tool in the Claude Engram MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on session_end? +

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

What risk level is session_end? +

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

Can I rate-limit session_end? +

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

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

session_end is provided by the Claude Engram MCP server (20alexl/claude-engram). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Claude Engram, and thousands of servers like it.

This server

All 16 Claude Engram tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →