Claim the next runnable task for a worker. Returns null if no task is currently runnable. Pass clientToken to make retries idempotent.
AI agents call claim_next_task to retrieve information from State Trace without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves the next available task from a work queue without creating, modifying, or deleting any data. It is a read-only operation consistent with 'get' or 'fetch' semantics. The low severity reflects minimal blast radius — claiming a task does not alter state in a way that causes damage if invoked incorrectly by an agent.
From the tool's definition Tool description states it 'Returns null if no task is currently runnable' and 'Claim the next runnable task' — this is a retrieval operation that fetches task state without modifying it.
Attacks that exploit this kind of access
Claim the next runnable task for a worker. Returns null if no task is currently runnable. Pass clientToken to make retries idempotent. It is categorised as a Read tool in the State Trace MCP Server, which means it retrieves data without modifying state.
Register the State Trace MCP server in PolicyLayer and add a rule for claim_next_task: 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 State Trace. Nothing to install.
claim_next_task 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 claim_next_task 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 claim_next_task. 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.
claim_next_task is provided by the State Trace MCP server (agent-pattern-labs/state-trace). 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 →