// SCAN REPORT

slurm_MCP

5 tools. 2 can modify or destroy data without limits.

2 write tools that can modify data. Rate limits recommended.

Last updated: 12 Jun 2026

2 can modify or destroy data

3 read-only

5 tools total

Community server · catalogue entry verified 12/06/2026

How to control slurm_MCP ↓

TOOL MAP

What slurm_MCP exposes to your agents

Read (3) Write / Execute (2) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous slurm_MCP tools

Execute · High submit_slurm_job Submitting a Slurm job causes external code/commands to execute on HPC cluster nodes, consuming compute resources and potentially running arbitrary scripts. Execute · High diagnose_error The server description explicitly mentions 'error diagnosis' as a capability.

2 of slurm_MCP's 5 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control slurm_MCP

PolicyLayer is an MCP gateway — it sits between your AI agents and slurm_MCP, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations

{
  "get_job_status": {
    "limits": [
      {
        "counter": "get_job_status_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register slurm_MCP — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON SLURM_MCP →

Free to start. No card required.

FULL CATALOGUE

All 5 slurm_MCP tools

EXECUTE 2 tools

Execute diagnose_error diagnose_error Execute submit_slurm_job submit_slurm_job

READ 3 tools

Read get_job_status Query the scheduler-visible status of a specific Slurm job. Read list_jobs list_jobs Read list_partitions List partitions and their basic scheduler state.

FAQ

Questions about slurm_MCP

Is the slurm_ MCP server safe to use without restrictions? +

The slurm_MCP server is primarily read-only with 3 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the slurm_ MCP server expose? +

5 tools across 2 categories: Read, Write. 3 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on slurm_MCP? +

Register the slurm_ MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every slurm_MCP tool call.

Deterministic rules across all 5 slurm_MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON SLURM_MCP →

Free to start. No card required.

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