Delete a specific analysis job by ID. DESTRUCTIVE: requires confirm=true.
AI agents call cortex_delete_job to permanently remove resources in Cortex — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes analysis job records, which cannot be undone. This is a classic destructive operation that irreversibly removes data. While the blast radius is somewhat limited to job records rather than critical production data, the explicit DESTRUCTIVE marking and deletion semantics place this in the Destructive category with high severity.
From the tool's definition Tool description explicitly states 'Delete a specific analysis job by ID' and marks it as 'DESTRUCTIVE'. The requirement for 'confirm=true' parameter confirms irreversible deletion.
Attacks that exploit this kind of access
Delete a specific analysis job by ID. DESTRUCTIVE: requires confirm=true. It is categorised as a Destructive tool in the Cortex MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Cortex MCP server in PolicyLayer and add a rule for cortex_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 Cortex. Nothing to install.
cortex_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 cortex_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 cortex_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.
cortex_delete_job is provided by the Cortex MCP server (solomonneas/cortex-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 →