Get the status of a specific SLURM job.
AI agents call get_job_status to retrieve information from Srunx without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool merely retrieves status information about an existing SLURM job without modifying, executing, or deleting anything. It is a straightforward query operation with no adverse impact potential.
From the tool's definition Tool name is 'get_job_status' and description states 'Get the status of a specific SLURM job.' The verb 'Get' and the read-only nature of status retrieval indicate no data 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 Srunx, 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.
Get the status of a specific SLURM job. It is categorised as a Read tool in the Srunx MCP Server, which means it retrieves data without modifying state.
Register the Srunx 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 Srunx. 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 Srunx MCP server (ksterx/srunx). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Srunx, 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.
14 Srunx tools catalogued and risk-classified — across an index of 43,000+ MCP servers.