AI agents use memento_handoff to create or update resources in Memento — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Memento environment.
This tool performs a write operation—it generates and persists a checkpoint—but produces no side effects beyond reversible state creation. It does not delete, destroy, or execute external operations. The low severity reflects limited blast radius: a malicious handoff prompt generation or checkpoint corruption would affect only the subsequent session context, not underlying data or external systems.
From the tool's definition Tool creates a checkpoint via 'Create a checkpoint' language, which involves writing/persisting state to the Memento system. The checkpoint mechanism stores a snapshot of the conversation/memory state.
Attacks that exploit this kind of access
[DEPRECATED] Create a checkpoint and generate an LLM-agnostic handoff prompt for continuing in a new chat. It is categorised as a Write tool in the Memento MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Memento MCP server in PolicyLayer and add a rule for memento_handoff: 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 Memento. Nothing to install.
memento_handoff 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 memento_handoff 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 memento_handoff. 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.
memento_handoff is provided by the Memento MCP server (joyciakira/memento). 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 →