Delete a workflow from the Morpheus automation library.
AI agents call delete_workflow to permanently remove resources in Morpheus MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of workflows from an automation library is irreversible and destructive. Once deleted, the workflow is removed from the system and cannot be recovered without backup/restore procedures. This impacts infrastructure automation and could disrupt dependent processes.
From the tool's definition The tool name 'delete_workflow' explicitly performs a deletion operation. The description states it will 'Delete a workflow from the Morpheus automation library,' which is an irreversible action that removes automation logic that may be relied upon by other…
Attacks that exploit this kind of access
Delete a workflow from the Morpheus automation library. It is categorised as a Destructive tool in the Morpheus MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Morpheus MCP Server 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 Morpheus MCP Server. 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 Morpheus MCP Server MCP server (nixndme/morpheus-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 →