Purge all managed job runs for a project, terminating known active runners first.
AI agents call jobs_purge to permanently remove resources in Run402 — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes job run data and forcibly terminates active runners—both of which cannot be undone. In the context of an autonomous infrastructure service for coding agents, purging all job runs would destroy audit trails, deployment history, and operational records that are typically immutable once committed. Forced termination of active runners could interrupt critical deployments or background work.
From the tool's definition 'Purge all managed job runs' and 'terminating' indicate irreversible deletion of job records and forced termination of active processes. The word 'purge' explicitly denotes permanent removal with no undo mechanism.
Attacks that exploit this kind of access
Purge all managed job runs for a project, terminating known active runners first. It is categorised as a Destructive tool in the Run402 MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Run402 MCP server in PolicyLayer and add a rule for jobs_purge: 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 Run402. Nothing to install.
jobs_purge 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 jobs_purge 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 jobs_purge. 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.
jobs_purge is provided by the Run402 MCP server (kychee-com/run402). 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 →