demo_undo_step

Remove the most recent step from the action script without undoing its effect

SERVERDemoday Claude Plugin SOURCEmrieck/demoday-claude-plugin

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/demoday-claude-plugin/demo-undo-step.md

WHAT IT DOES

What demo_undo_step does on Demoday Claude Plugin

AI agents call demo_undo_step to permanently remove resources in Demoday Claude Plugin, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why demo_undo_step is rated Critical

Irreversibly deletes a recorded script step with no way to undo the removal.

From the tool's definition Remove the most recent step from the action script

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs demo_undo_step safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Demoday Claude Plugin, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For demo_undo_step, this is the rule to start with:

demo_undo_step Hidden

demo_undo_step is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "demo_undo_step"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Demoday Claude Plugin, apply this rule, and every demo_undo_step call is checked against it from then on.

FAQ

Questions about demo_undo_step

What does the demo_undo_step tool do? +

Remove the most recent step from the action script without undoing its effect. It is categorised as a Destructive tool in the Demoday Claude Plugin MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on demo_undo_step? +

Register the Demoday Claude Plugin MCP server in PolicyLayer and add a rule for demo_undo_step: 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 Demoday Claude Plugin. Nothing to install.

What risk level is demo_undo_step? +

demo_undo_step is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit demo_undo_step? +

Yes. Add a rate_limit block to the demo_undo_step 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.

How do I block demo_undo_step completely? +

Set action: deny in the PolicyLayer policy for demo_undo_step. 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.

What MCP server provides demo_undo_step? +

demo_undo_step is provided by the Demoday Claude Plugin MCP server (mrieck/demoday-claude-plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Demoday Claude Plugin, and thousands of servers like it.

This server

All 16 Demoday Claude Plugin tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →