End the current episode. This generates a summary and extracts key entities and topics.
AI agents use memory_episode_end to create or update resources in MCP Router — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Router environment.
Ending an episode triggers the generation and storage of a summary along with entity/topic extraction — this modifies/creates persisted data (the episode summary and extracted entities). It is reversible in principle (the episode record could be deleted), so Write is more appropriate than Destructive.
From the tool's definition End the current episode. This generates a summary and extracts key entities and topics.
Attacks that exploit this kind of access
End the current episode. This generates a summary and extracts key entities and topics. It is categorised as a Write tool in the MCP Router MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Router MCP server in PolicyLayer and add a rule for memory_episode_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 MCP Router. Nothing to install.
memory_episode_end 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_episode_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.
Set action: deny in the PolicyLayer policy for memory_episode_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.
memory_episode_end is provided by the MCP Router MCP server (justinpreston/mcp-router). 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 →