Get current status of the undo system (checkpoint count, number of checkpoints in the stack, and whether undo is possible)
AI agents call status 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 retrieves and reports the current state of the undo system. It performs no modifications, deletions, code execution, or irreversible actions. It is a pure information-gathering operation, fitting the Read category with low severity since misuse poses minimal risk.
From the tool's definition Tool name 'status' and description 'Get current status' indicates retrieval of system information without modification or side effects. Returns checkpoint count, stack information, and boolean state—all read-only queries.
Documented attack patterns abuse exactly the kind of access status 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 status:
{
"version": "1",
"default": "deny",
"tools": {
"status": {}
}
}status 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.
Get current status of the undo system (checkpoint count, number of checkpoints in the stack, and whether undo is possible). 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 status: 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.
status 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 status 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 status. 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.
status 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.