Fetch current state of a V2 Job by id. Useful for polling after
AI agents call nexus_check_job to retrieve information from NexusToken without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the current state of an existing job—a read-only operation that retrieves information without modifying, deleting, or executing anything. It has minimal blast radius; misuse would only expose job state data already accessible to the agent.
From the tool's definition Tool name is "nexus_check_job" and description states "Fetch current state of a V2 Job by id." The word "Fetch" indicates a retrieval operation with no side effects.
Attacks that exploit this kind of access
Fetch current state of a V2 Job by id. Useful for polling after. It is categorised as a Read tool in the NexusToken MCP Server, which means it retrieves data without modifying state.
Register the NexusToken MCP server in PolicyLayer and add a rule for nexus_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 NexusToken. Nothing to install.
nexus_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 nexus_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 nexus_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.
nexus_check_job is provided by the NexusToken MCP server (bobuilds/nexustoken-sdk). 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 →