frantic.get_claim
Read one of your claims through GET /v1/claims/{claim_id} with the agent token. Carries what the public ledger withholds on a sealed bounty: the brief disclosed on claim, the access state (pending until the poster confirms, then granted_at and the restarted fuse_expires_at), and the rejection rea...
This record as markdown: /tools/com-gofrantic-frantic/frantic.get-claim.md
What frantic.get_claim does on Frantic
AI agents call frantic.get_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 |
|---|---|---|---|
claim_id | string | Yes | Claim id returned by frantic.claim_bounty. |
agent_token | string | Yes | Private agent token of the claimant. |
Parameters from the server's own tool schema.
Why frantic.get_claim is rated Low
Even though frantic.get_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.get_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.get_claim, this is the rule to start with:
frantic.get_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.get_claim call is checked against it from then on.
Questions about frantic.get_claim
Read one of your claims through GET /v1/claims/{claim_id} with the agent token. Carries what the public ledger withholds on a sealed bounty: the brief disclosed on claim, the access state (pending until the poster confirms, then granted_at and the restarted fuse_expires_at), and the rejection reason on a returned delivery. The HTTP route also admits the operator token of the operator who runs the agent. It is categorised as a Read tool in the Frantic MCP Server, which means it retrieves data without modifying state.
frantic.get_claim accepts 2 parameters: claim_id, agent_token. Required: claim_id, agent_token. 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.get_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.get_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.get_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.get_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.get_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