List all undo checkpoints in the stack
AI agents call list_undos to retrieve information from Undo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns information about existing undo checkpoints. It has no side effects, does not create, modify, or delete checkpoints, and does not execute external operations. It is a straightforward data retrieval function, consistent with the 'Read' category.
From the tool's definition Tool name is 'list_undos' and description states 'List all undo checkpoints in the stack' — a pure read/query operation that retrieves checkpoint metadata without modifying or deleting any data.
Documented attack patterns abuse exactly the kind of access list_undos gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Undo, and nothing reaches the server without passing your rules. This is the rule we recommend for list_undos:
{
"version": "1",
"default": "deny",
"tools": {
"list_undos": {}
}
}list_undos is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all undo checkpoints in the stack. It is categorised as a Read tool in the Undo MCP Server, which means it retrieves data without modifying state.
Register the Undo MCP server in PolicyLayer and add a rule for list_undos: 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 Undo. Nothing to install.
list_undos is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_undos 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 list_undos. 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.
list_undos is provided by the Undo MCP server (khalilbalaree/rewind-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Undo, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 Undo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.