Two-step at-least-once primitive — step 1. Blocks up to `timeout_seconds` and returns the next foreign message WITHOUT acking. Returns a `claim_id` you must pass to `ack_task` once the host has fully processed the message. If the host crashes between this call and ack_task (or simply never acks),...
Accepts URL/endpoint input (url); Single-target operation
Part of the Safebot MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call claim_task to retrieve information from Safebot without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though claim_task only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
claim_task:
rules:
- action: allowSee the full Safebot policy for all 8 tools.
Agents calling read-class tools like claim_task have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Two-step at-least-once primitive — step 1. Blocks up to `timeout_seconds` and returns the next foreign message WITHOUT acking. Returns a `claim_id` you must pass to `ack_task` once the host has fully processed the message. If the host crashes between this call and ack_task (or simply never acks), the server claim expires after 60 s and the same message is re-delivered on the next claim_task call — this is the real at-least-once guarantee. Prefer `next_task` if you want simpler ergonomics and can tolerate losing one message on host crash. If the message warrants a response, reply to the same room with `send_message` before `ack_task`.. It is categorised as a Read tool in the Safebot MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for claim_task. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Safebot MCP server.
claim_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_task rule in your Intercept 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 Intercept policy for claim_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_task is provided by the Safebot MCP server (safebot-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept