cancel_slurm_job

Cancel a running or pending Slurm job.

SERVERCLIO Adios SOURCEpypi:clio-kit

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/io-github-iowarp-adios-mcp/cancel-slurm-job.md

WHAT IT DOES

What cancel_slurm_job does on CLIO Adios

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

RISK

Why cancel_slurm_job is rated Critical

Cancelling a Slurm job is an irreversible action — a terminated job loses its execution state, queued work, and any in-progress computation cannot be resumed from where it was stopped. This is a destructive operation with potentially high blast radius if a long-running scientific compute job is terminated prematurely.

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

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs cancel_slurm_job safely

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

cancel_slurm_job Hidden

cancel_slurm_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_slurm_job"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect CLIO Adios, apply this rule, and every cancel_slurm_job call is checked against it from then on.

FAQ

Questions about cancel_slurm_job

What does the cancel_slurm_job tool do? +

Cancel a running or pending Slurm job. It is categorised as a Destructive tool in the CLIO Adios 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_slurm_job? +

Register the CLIO Adios MCP server in PolicyLayer and add a rule for cancel_slurm_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 CLIO Adios. Nothing to install.

What risk level is cancel_slurm_job? +

cancel_slurm_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_slurm_job? +

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

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

cancel_slurm_job is provided by the CLIO Adios MCP server (pypi:clio-kit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CLIO Adios, and thousands of servers like it.

This server

All 204 CLIO Adios 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 code and CI agents →Blast radius →Tool call approval →