cancel_background_job

Cancel a running background job.

SERVERSSH MCP Server SOURCEbhayanak/ssh-mcp-server

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/bhayanak-ssh-mcp-server/cancel-background-job.md

WHAT IT DOES

What cancel_background_job does on SSH MCP Server

AI agents call cancel_background_job to permanently remove resources in SSH MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why cancel_background_job is rated Critical

Cancelling a running background job is an irreversible action — the job's in-progress work is terminated and cannot be resumed. This can have significant downstream consequences depending on what the job was doing (e.g., deployments, certificate issuance, configuration changes). The action itself cannot be undone, placing it in the Destructive category with high severity given the remote server management context.

From the tool's definition Cancel a running background job

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs cancel_background_job safely

PolicyLayer is an MCP gateway: it sits between your AI agents and SSH MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cancel_background_job, this is the rule to start with:

cancel_background_job Hidden

cancel_background_job is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

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

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect SSH MCP Server, apply this rule, and every cancel_background_job call is checked against it from then on.

FAQ

Questions about cancel_background_job

What does the cancel_background_job tool do? +

Cancel a running background job. It is categorised as a Destructive tool in the SSH MCP Server 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_background_job? +

Register the SSH MCP Server MCP server in PolicyLayer and add a rule for cancel_background_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 SSH MCP Server. Nothing to install.

What risk level is cancel_background_job? +

cancel_background_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_background_job? +

Yes. Add a rate_limit block to the cancel_background_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_background_job completely? +

Set action: deny in the PolicyLayer policy for cancel_background_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_background_job? +

cancel_background_job is provided by the SSH MCP Server MCP server (bhayanak/ssh-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on SSH MCP Server, and thousands of servers like it.

This server

All 23 SSH MCP Server tools → Critical-risk tools on this server →

Across the catalogue

sms_cancel_scheduled on Twilio SMS MCP Server →cancel_all_orders on Lighter MCP →delete_cron_job on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →