Show all SLURM jobs currently in the queue for this user
AI agents call job_status to retrieve information from Tacc Mcp Bio without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the SLURM job queue to display status information for the user's jobs. It has no side effects, does not execute code, does not modify data, and does not delete or move resources. It is purely informational retrieval, fitting the Read category. Severity is low because misuse would only expose job metadata already visible to the user.
From the tool's definition Tool name 'job_status' and description 'Show all SLURM jobs currently in the queue for this user' indicate a read-only query operation that retrieves status information without modifying or executing anything.
Attacks that exploit this kind of access
Show all SLURM jobs currently in the queue for this user. It is categorised as a Read tool in the Tacc Mcp Bio MCP Server, which means it retrieves data without modifying state.
Register the Tacc Mcp Bio MCP server in PolicyLayer and add a rule for 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 Tacc Mcp Bio. Nothing to install.
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 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 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.
job_status is provided by the Tacc Mcp Bio MCP server (narasimhan-lab/tacc-mcp-bio). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →