AI agents call list_jobs 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.
list_jobs retrieves job information from a Slurm cluster without modifying, deleting, or executing arbitrary operations. It fits the Read category as it queries data with no side effects. Severity is low because unauthorized job listing carries minimal risk—it reveals job metadata but not sensitive computation data or cluster vulnerabilities.
From the tool's definition Tool name 'list_jobs' indicates a query/retrieval operation on a Slurm HPC cluster. The description is empty, but context from sibling tools (get_job_status, list_partitions, diagnose_error, submit_slurm_job) and the server purpose confirm this is a…
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 slurm_MCP, 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_jobs. 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 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 slurm_MCP. 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 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.