mcp__automation__delete_automation
删除 DutyDeck 定时任务。只在用户明确要求删除，或任务已经长期无价值且用户确认后使用。
This record as markdown: /tools/dutydeck/mcp--automation--delete-automation.md
What mcp__automation__delete_automation does on DutyDeck
AI agents call mcp__automation__delete_automation to permanently remove resources in DutyDeck, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why mcp__automation__delete_automation is rated Critical
An AI agent that decides to call mcp__automation__delete_automation doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from DutyDeck is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs mcp__automation__delete_automation safely
PolicyLayer is an MCP gateway: it sits between your AI agents and DutyDeck, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mcp__automation__delete_automation, this is the rule to start with:
mcp__automation__delete_automation is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect DutyDeck, apply this rule, and every mcp__automation__delete_automation call is checked against it from then on.
Questions about mcp__automation__delete_automation
删除 DutyDeck 定时任务。只在用户明确要求删除，或任务已经长期无价值且用户确认后使用。. It is categorised as a Destructive tool in the DutyDeck MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the DutyDeck MCP server in PolicyLayer and add a rule for mcp__automation__delete_automation: 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 DutyDeck. Nothing to install.
mcp__automation__delete_automation is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the mcp__automation__delete_automation 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 mcp__automation__delete_automation. 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.
mcp__automation__delete_automation is provided by the DutyDeck MCP server (taokoplay/DutyDeck). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on DutyDeck, and thousands of servers like it.
Across the catalogue