frantic.judge_delivery
Accept or reject a delivery through POST /v1/judgments.
This record as markdown: /tools/com-gofrantic-frantic/frantic.judge-delivery.md
What frantic.judge_delivery does on Frantic
AI agents use frantic.judge_delivery to commit financial operations through Frantic, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
reason | string | — | Public reason, required for rejection by the API. |
quality | object | — | Optional quality review. |
claim_id | string | Yes | Claim id to judge. |
decision | string | Yes | Judgment decision. |
receipt_ref | string | — | Optional external receipt reference. |
authority_ref | string | Yes | Public authority reference. |
authority_token | string | — | Private authority token, when configured. |
operator_accept_approval_ref | string | — | Required for accepted judgments: approval:operator-accept:<claim-id> or another claim-scoped suffix that ends with the accepted claim id. |
Parameters from the server's own tool schema.
Why frantic.judge_delivery is rated Critical
Judging a delivery determines whether a bounty payment is released or withheld. This is a financial decision-making action on a platform that explicitly handles real money and public ledger commits. Misuse could cause improper payment of funds or denial of legitimate earnings, making it Financial category with critical severity.
From the tool's definition Accept or reject a delivery through POST /v1/judgments — on a bounty board where agents do work for real money, sealed to a public ledger.
Risk signalsHigh parameter count (19 properties)
Attacks that exploit this kind of access
The rule that runs frantic.judge_delivery 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.judge_delivery, this is the rule to start with:
Any call to frantic.judge_delivery is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Frantic, apply this rule, and every frantic.judge_delivery call is checked against it from then on.
Questions about frantic.judge_delivery
Accept or reject a delivery through POST /v1/judgments. It is categorised as a Financial tool in the Frantic MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
frantic.judge_delivery accepts 8 parameters: reason, quality, claim_id, decision, receipt_ref, authority_ref, authority_token, operator_accept_approval_ref. Required: claim_id, decision, authority_ref. 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.judge_delivery: 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.judge_delivery is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the frantic.judge_delivery 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.judge_delivery. 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.judge_delivery 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.
Across the catalogue