Get queued jobs data.
AI agents call get_queued_jobs_resource to retrieve information from PyTorch HUD MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries queued jobs status from the PyTorch CI/CD system without creating, modifying, executing, deleting, or affecting any financial state. It is a pure read operation with minimal blast radius—returning job queue information poses no risk of side effects or data modification.
From the tool's definition Tool name 'get_queued_jobs_resource' and description 'Get queued jobs data' indicate a retrieval operation with no modification or execution capability. The verb 'Get' is explicitly a read operation that queries existing CI/CD job queue status.
Attacks that exploit this kind of access
Get queued jobs data. It is categorised as a Read tool in the PyTorch HUD MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PyTorch HUD MCP Server MCP server in PolicyLayer and add a rule for get_queued_jobs_resource: 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 PyTorch HUD MCP Server. Nothing to install.
get_queued_jobs_resource 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_queued_jobs_resource 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_queued_jobs_resource. 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_queued_jobs_resource is provided by the PyTorch HUD MCP Server MCP server (izaitsevfb/claude-pytorch-treehugger). 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 →