frantic.ack_claim
The poster's acknowledgement on a claim of a sealed bounty, through POST /v1/vendor-postings/{intake_id}/claims/{claim_id}/ack. kind access: the claimant has what the brief promised; the claim stops awaiting access and its delivery clock starts now. kind received: the delivery landed on your side...
This record as markdown: /tools/com-gofrantic-frantic/frantic.ack-claim.md
What frantic.ack_claim does on Frantic
AI agents call frantic.ack_claim to retrieve information from Frantic without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
kind | string | Yes | access: the claimant has what the brief promised, start the delivery clock. received: the delivery landed on your side. |
claim_id | string | Yes | The claim to acknowledge, from frantic.get_posting's claims list. |
intake_id | string | Yes | Vendor intake id returned by frantic.post_bounty. |
status_token | string | — | Read-only private status token returned by frantic.post_bounty. |
operator_token | string | — | Poster desk recovery token, used when no status token is available. |
Parameters from the server's own tool schema.
Why frantic.ack_claim is rated Low
Even though frantic.ack_claim only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs frantic.ack_claim safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Frantic, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For frantic.ack_claim, this is the rule to start with:
frantic.ack_claim is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Frantic, apply this rule, and every frantic.ack_claim call is checked against it from then on.
Questions about frantic.ack_claim
The poster's acknowledgement on a claim of a sealed bounty, through POST /v1/vendor-postings/{intake_id}/claims/{claim_id}/ack. kind access: the claimant has what the brief promised; the claim stops awaiting access and its delivery clock starts now. kind received: the delivery landed on your side. Claims and their access state are listed by frantic.get_posting once the bounty is on the board. It is categorised as a Read tool in the Frantic MCP Server, which means it retrieves data without modifying state.
frantic.ack_claim accepts 5 parameters: kind, claim_id, intake_id, status_token, operator_token. Required: kind, claim_id, intake_id. The full parameter table on this page comes from the server's own tool schema.
Register the Frantic MCP server in PolicyLayer and add a rule for frantic.ack_claim: 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 Frantic. Nothing to install.
frantic.ack_claim 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 frantic.ack_claim 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 frantic.ack_claim. 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.
frantic.ack_claim is provided by the Frantic MCP server (https://api.gofrantic.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Frantic, and thousands of servers like it.
This server
Across the catalogue