Check the status of a background agent job.
AI agents call check_job to retrieve information from Vending Machine without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the state of an existing background job. It retrieves information only and produces no side effects, modifications, or execution of code. Status checks are non-destructive read operations with minimal blast radius even if misused by an AI agent.
From the tool's definition Tool name 'check_job' and description 'Check the status of a background agent job' indicate a read-only operation that retrieves job status information without modification or execution.
Attacks that exploit this kind of access
Check the status of a background agent job. It is categorised as a Read tool in the Vending Machine MCP Server, which means it retrieves data without modifying state.
Register the Vending Machine MCP server in PolicyLayer and add a rule for check_job: 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 Vending Machine. Nothing to install.
check_job 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 check_job 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 check_job. 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.
check_job is provided by the Vending Machine MCP server (yokiidesu/vending-machine-mcp). 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 →