rollback_memory_supersession_run
Execute guarded rollback for a Memory v3 supersession apply run.
This record as markdown: /tools/mapi-agent-memory/rollback-memory-supersession-run.md
What rollback_memory_supersession_run does on Mapi Agent Memory
AI agents invoke rollback_memory_supersession_run to trigger actions in Mapi Agent Memory. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why rollback_memory_supersession_run is rated High
This tool executes a rollback operation on memory state management within an AI agent system. While guarded and likely reversible in intent, the action itself triggers external state modifications and potentially complex side effects on agent memory structures.
From the tool's definition Tool name contains 'Execute' verb 'rollback' and description states 'Execute guarded rollback for a Memory v3 supersession apply run' — the word 'Execute' combined with the action of rolling back a memory supersession run indicates triggering an external…
Attacks that exploit this kind of access
The rule that runs rollback_memory_supersession_run safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mapi Agent Memory, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For rollback_memory_supersession_run, this is the rule to start with:
rollback_memory_supersession_run stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mapi Agent Memory, apply this rule, and every rollback_memory_supersession_run call is checked against it from then on.
Questions about rollback_memory_supersession_run
Execute guarded rollback for a Memory v3 supersession apply run. It is categorised as a Execute tool in the Mapi Agent Memory MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mapi Agent Memory MCP server in PolicyLayer and add a rule for rollback_memory_supersession_run: 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 Mapi Agent Memory. Nothing to install.
rollback_memory_supersession_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the rollback_memory_supersession_run 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 rollback_memory_supersession_run. 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.
rollback_memory_supersession_run is provided by the Mapi Agent Memory MCP server (cabo0m/mapi-agent-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mapi Agent Memory, and thousands of servers like it.
Across the catalogue