slurm_describe

Return a unified description of one scheduler-native Slurm job.

SERVERCLIO Adios SOURCEpypi:clio-kit

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-iowarp-adios-mcp/slurm-describe.md

WHAT IT DOES

What slurm_describe does on CLIO Adios

AI agents call slurm_describe to retrieve information from CLIO Adios without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why slurm_describe is rated Low

Even though slurm_describe only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs slurm_describe 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 slurm_describe, this is the rule to start with:

slurm_describe Allowed

slurm_describe is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "slurm_describe": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about slurm_describe

What does the slurm_describe tool do? +

Return a unified description of one scheduler-native Slurm job. It is categorised as a Read tool in the CLIO Adios MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on slurm_describe? +

Register the CLIO Adios MCP server in PolicyLayer and add a rule for slurm_describe: 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 slurm_describe? +

slurm_describe is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit slurm_describe? +

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

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

slurm_describe 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 →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →