undo_run
A execute tool on the Mapi Agent Memory MCP server.
This record as markdown: /tools/mapi-agent-memory/undo-run.md
What undo_run does on Mapi Agent Memory
AI agents invoke undo_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 undo_run is rated High
Despite empty description, the tool name 'undo_run' in a memory governance context indicates it executes a reversal/rollback operation rather than passively reading data. Rollback operations are Execute rather than Write (irreversible in some cases) because their primary purpose is to trigger a system action with dependencies on context.
From the tool's definition Tool name 'undo_run' in context of auditable memory governance system. The sibling tools show this server manages memory state transitions (apply_*, apply_memory_*).
Attacks that exploit this kind of access
The rule that runs undo_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 undo_run, this is the rule to start with:
undo_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 undo_run call is checked against it from then on.
Questions about undo_run
undo_run is a execute tool on the Mapi Agent Memory MCP server. 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 undo_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.
undo_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 undo_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 undo_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.
undo_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