Critical Risk →

cancel_job

Cancel a running or pending background job.

How to control cancel_job ↓

What cancel_job does on Sktime

AI agents call cancel_job to permanently remove resources in Sktime — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why cancel_job needs a policy

Cancelling a job is an irreversible action — once cancelled, the in-progress computation is terminated and cannot be resumed. This is analogous to destroying running state, making it Destructive. Severity is medium since it affects a background job but does not delete persisted data.

From the tool's definition Cancel a running or pending background job

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

How to control cancel_job

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

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "cancel_job"
  ]
}

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

  1. Create a free account and register Sktime — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about cancel_job

What does the cancel_job tool do? +

Cancel a running or pending background job. It is categorised as a Destructive tool in the Sktime 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 cancel_job? +

Register the Sktime 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 Sktime. Nothing to install.

What risk level is cancel_job? +

cancel_job 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 cancel_job? +

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.

How do I block cancel_job completely? +

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.

What MCP server provides cancel_job? +

cancel_job is provided by the Sktime MCP server (sktime/sktime-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Sktime tool call.

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

Free to start. No card required.

24 Sktime tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.