Delete an automation job.
AI agents call delete_job 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.
Deleting a job is an irreversible operation that destroys data/configuration. This falls squarely into the Destructive category per the definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' In a cloud infrastructure management context (HPE Morpheus), deleting automation jobs could disrupt critical workflows, impact multiple tenants, and have cascading effects, warranting high…
From the tool's definition Tool name 'delete_job' explicitly indicates deletion of an automation job, which is irreversible. The description states it will 'Delete an automation job,' confirming destructive intent with no undo capability.
Attacks that exploit this kind of access
Delete an automation job. 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_job: 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_job 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_job 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_job. 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_job 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 →