AI agents call delete_workflow_tool to permanently remove resources in Openowl — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs a delete operation on saved workflows, which cannot be undone. This is a destructive action that permanently removes user data. While the blast radius is somewhat limited to workflows rather than system-wide data, the irreversible nature and potential loss of user work justifies the 'Destructive' category and 'high' severity rating.
From the tool's definition Tool name 'delete_workflow_tool' with description 'Delete a saved workflow' indicates irreversible deletion of user-created data.
Documented attack patterns abuse exactly the kind of access delete_workflow_tool gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Openowl, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_workflow_tool:
{
"version": "1",
"default": "deny",
"hide": [
"delete_workflow_tool"
]
}delete_workflow_tool disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a saved workflow. It is categorised as a Destructive tool in the Openowl MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Openowl MCP server in PolicyLayer and add a rule for delete_workflow_tool: 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 Openowl. Nothing to install.
delete_workflow_tool 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_tool 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_tool. 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_tool is provided by the Openowl MCP server (mihir-kanzariya/openowl). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Openowl, 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.
40 Openowl tools catalogued and risk-classified — across an index of 43,000+ MCP servers.