Cancel a running or queued job. Working_dir is preserved for inspection.
AI agents call cancel_job to permanently remove resources in Vimax — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cancelling a job is an irreversible action — the job cannot be resumed once cancelled. While the working directory is preserved for inspection, the job execution itself is permanently terminated, making this a destructive operation. Severity is medium because the blast radius is limited to a single job (no data deletion, no financial impact), but the cancelled work cannot be undone.
From the tool's definition Cancel a running or queued job
Attacks that exploit this kind of access
Cancel a running or queued job. Working_dir is preserved for inspection. It is categorised as a Destructive tool in the Vimax MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Vimax MCP server in PolicyLayer and add a rule for cancel_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 Vimax. Nothing to install.
cancel_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 cancel_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 cancel_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.
cancel_job is provided by the Vimax MCP server (zcdeng/vimax-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 →