llm_job_cancel

THE RISK

Critical Risk

Why llm_job_cancel needs a policy

Cancelling a running job is irreversible — the in-progress computation is terminated and cannot be resumed. This matches the Destructive category (irreversible action). Severity is medium because the blast radius is limited to losing the results of a single job rather than data deletion or financial impact.

From the tool's definition Cancel a running gateway async or deferred-sync job by jobId

Documented attack patterns abuse exactly the kind of access llm_job_cancel gives an agent:

POLICY

How to control llm_job_cancel

PolicyLayer is an MCP gateway — it sits between your AI agents and LLM CLI Gateway, and nothing reaches the server without passing your rules. This is the rule we recommend for llm_job_cancel:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "llm_job_cancel"
  ]
}

llm_job_cancel disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register LLM CLI Gateway — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More LLM CLI Gateway tools

Destructive session_clear_all Delete all gateway session records, optionally scoped to one provider. Destructive session_delete Delete a gateway session record by ID (also removes any gateway-owned worktree attached to Execute claude_request Run a Claude Code CLI request synchronously (when async jobs are enabled, auto-defers to a Execute claude_request_async Start a Claude Code CLI request as a durable background job. Poll with llm_job_status, col Execute cli_upgrade Plan (dryRun, default true) or execute an upgrade for one provider CLI using its native up Execute codex_fork_session Fork an existing Codex session into a new branch (codex fork <ID|--last>) and run a prompt Execute codex_request Run an OpenAI Codex CLI request synchronously (when async jobs are enabled, auto-defers to Execute codex_request_async Start an OpenAI Codex CLI request as a durable background job. Poll with llm_job_status, c

All 46 LLM CLI Gateway tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in LLM CLI Gateway → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about llm_job_cancel

What does the llm_job_cancel tool do? +

Cancel a running gateway async or deferred-sync job by jobId. It is categorised as a Destructive tool in the LLM CLI Gateway MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on llm_job_cancel? +

Register the LLM CLI Gateway MCP server in PolicyLayer and add a rule for llm_job_cancel: 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 LLM CLI Gateway. Nothing to install.

What risk level is llm_job_cancel? +

llm_job_cancel is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit llm_job_cancel? +

Yes. Add a rate_limit block to the llm_job_cancel 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.

How do I block llm_job_cancel completely? +

Set action: deny in the PolicyLayer policy for llm_job_cancel. 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.

What MCP server provides llm_job_cancel? +

llm_job_cancel is provided by the LLM CLI Gateway MCP server (llm-cli-gateway). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every LLM CLI Gateway tool call.

Start from LLM CLI Gateway, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →