Query the scheduler-visible status of a specific Slurm job.
AI agents call get_job_status to retrieve information from slurm_MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries job status information from the Slurm scheduler without creating, modifying, deleting, or executing any operations. It is a pure read operation that retrieves scheduler metadata. The low severity reflects minimal blast radius—misuse would only expose job status visibility, not compromise cluster integrity or enable unauthorized operations.
From the tool's definition Tool name 'get_job_status' and description 'Query the scheduler-visible status of a specific Slurm job' indicate data retrieval with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_job_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and slurm_MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_job_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_job_status": {}
}
}get_job_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Query the scheduler-visible status of a specific Slurm job. It is categorised as a Read tool in the slurm_MCP MCP Server, which means it retrieves data without modifying state.
Register the slurm_ MCP server in PolicyLayer and add a rule for get_job_status: 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 slurm_MCP. Nothing to install.
get_job_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_job_status 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.
Set action: deny in the PolicyLayer policy for get_job_status. 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.
get_job_status is provided by the slurm_ MCP server (pengc0066-star/slurm_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from slurm_MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 slurm_MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.