delete_workflow_trigger

Delete a workflow trigger.

SERVERTodo for AI MCP Server SOURCEtodo-for-ai/todo-for-ai-mcp

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/todo-for-ai-todo-for-ai-mcp/delete-workflow-trigger.md

WHAT IT DOES

What delete_workflow_trigger does on Todo for AI MCP Server

AI agents call delete_workflow_trigger to permanently remove resources in Todo for AI MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why delete_workflow_trigger is rated Critical

An AI agent that decides to call delete_workflow_trigger doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Todo for AI MCP Server is gone. There is no undo for destructive operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_workflow_trigger safely

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

delete_workflow_trigger Hidden

delete_workflow_trigger 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": [
    "delete_workflow_trigger"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Todo for AI MCP Server, apply this rule, and every delete_workflow_trigger call is checked against it from then on.

FAQ

Questions about delete_workflow_trigger

What does the delete_workflow_trigger tool do? +

Delete a workflow trigger. It is categorised as a Destructive tool in the Todo for AI MCP Server 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 delete_workflow_trigger? +

Register the Todo for AI MCP Server MCP server in PolicyLayer and add a rule for delete_workflow_trigger: 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 Todo for AI MCP Server. Nothing to install.

What risk level is delete_workflow_trigger? +

delete_workflow_trigger 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 delete_workflow_trigger? +

Yes. Add a rate_limit block to the delete_workflow_trigger 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 delete_workflow_trigger completely? +

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

delete_workflow_trigger is provided by the Todo for AI MCP Server MCP server (todo-for-ai/todo-for-ai-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Todo for AI MCP Server, and thousands of servers like it.

This server

All 244 Todo for AI MCP Server tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →