// MCP TOOL REFERENCE

SRUNX TOOLS

14 tools from the Srunx MCP Server, categorised by risk level.

// ALL 14 SRUNX TOOLS

READ 9 tools

Read get_config Get the current srunx configuration including resource defaults and environment settings. Read get_job_logs Get stdout/stderr logs for a SLURM job. Read get_job_status Get the status of a specific SLURM job. Read get_resources Get current GPU and node resource availability on the SLURM cluster. Read get_workflow Read and parse a workflow YAML file, returning its full structure. Read list_jobs List current user's SLURM jobs in the queue. Read list_ssh_profiles List all configured SSH connection profiles for remote SLURM clusters. Read list_workflows List workflow YAML files in a directory. Read validate_workflow Validate a workflow YAML file for correctness.

WRITE 2 tools

Write sync_files sync_files Write create_workflow create_workflow

DESTRUCTIVE 1 tools

Destructive cancel_job Cancel a running or pending SLURM job.

EXECUTE 2 tools

Execute run_workflow run_workflow Execute submit_job submit_job

// FAQ

How many tools does the Srunx MCP server have? +

The Srunx MCP server exposes 14 tools across 4 categories: Read, Write, Destructive, Execute.

How do I enforce policies on Srunx tools? +

Route the Srunx server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard; they are enforced on every call before it reaches the server.

What risk categories do Srunx tools fall into? +

Srunx tools are categorised as Read (9), Write (2), Destructive (1), Execute (2). Each category has a recommended default policy.

Enforce policy on every Srunx tool call.

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

CHECK YOUR STACK →

Free to start. No card required.

43,000+ MCP servers and 220,000+ tools scanned and risk-classified.