Delete a scheduled workflow by id.
AI agents call delete_workflow to permanently remove resources in Crosswalk — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes a workflow from the system. Once deleted, the workflow configuration, schedule, and associated state are lost and cannot be recovered without manual restoration. This is a destructive operation with potential blast radius: an agent could accidentally delete critical job application workflows, disrupting a user's career pipeline automation.
From the tool's definition Tool name 'delete_workflow' and description 'Delete a scheduled workflow by id' — the verb 'Delete' combined with the irreversible nature of removing a scheduled workflow.
Attacks that exploit this kind of access
Delete a scheduled workflow by id. It is categorised as a Destructive tool in the Crosswalk MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Crosswalk MCP server in PolicyLayer and add a rule for delete_workflow: 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 Crosswalk. Nothing to install.
delete_workflow 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 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. 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 is provided by the Crosswalk MCP server (mohakgarg5/crosswalk-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →