List current user's SLURM jobs in the queue.
AI agents call list_jobs 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 retrieves and displays existing job information from the SLURM queue. It performs no creation, modification, deletion, or execution of jobs. The only permission required is read access to the user's own job metadata. Misuse would have minimal blast radius — an agent could only learn about existing jobs, not affect them.
From the tool's definition Tool description states 'List current user's SLURM jobs in the queue' — a purely informational retrieval operation with no side effects. The verb 'list' and the action of querying job status without modification indicate read-only behavior.
Documented attack patterns abuse exactly the kind of access list_jobs 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 list_jobs:
{
"version": "1",
"default": "deny",
"tools": {
"list_jobs": {}
}
}list_jobs 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.
List current user's SLURM jobs in the queue. 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 list_jobs: 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.
list_jobs 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 list_jobs 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 list_jobs. 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.
list_jobs 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.