delete_workflow_execution
Delete a workflow execution session. This cannot be undone.
This record as markdown: /tools/namastexlabs-automagik-tools/delete-workflow-execution.md
What delete_workflow_execution does on Automagik Tools
AI agents call delete_workflow_execution to permanently remove resources in Automagik Tools, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_workflow_execution is rated Critical
This tool permanently deletes workflow execution data with no recovery option. While not financial or involving code execution, the irreversible nature of deletion and the potential impact on workflow history and auditing make this a Destructive operation. The high severity reflects that an AI agent could inadvertently erase important workflow records or session data that business operations depend on.
From the tool's definition Tool description explicitly states 'Delete a workflow execution session. This cannot be undone.' The verb 'Delete' combined with 'cannot be undone' clearly indicates irreversible data destruction.
Attacks that exploit this kind of access
The rule that runs delete_workflow_execution safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Automagik Tools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_workflow_execution, this is the rule to start with:
delete_workflow_execution 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 Automagik Tools, apply this rule, and every delete_workflow_execution call is checked against it from then on.
Questions about delete_workflow_execution
Delete a workflow execution session. This cannot be undone. It is categorised as a Destructive tool in the Automagik Tools MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Automagik Tools MCP server in PolicyLayer and add a rule for delete_workflow_execution: 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 Automagik Tools. Nothing to install.
delete_workflow_execution 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 delete_workflow_execution 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 delete_workflow_execution. 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.
delete_workflow_execution is provided by the Automagik Tools MCP server (namastexlabs/automagik-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Automagik Tools, and thousands of servers like it.
Across the catalogue