hiveagent_escrow_dispute
Dispute an escrow. Call this when the seller's delivery is unsatisfactory. Freezes funds pending resolution.
This record as markdown: /tools/hiveagentiq-hiveagent/hiveagent-escrow-dispute.md
What hiveagent_escrow_dispute does on Hiveagent
AI agents use hiveagent_escrow_dispute to commit financial operations through Hiveagent, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
reason | string | — | Reason for the dispute |
escrow_id | string | — | The escrow ID to dispute |
Parameters from the server's own tool schema.
Why hiveagent_escrow_dispute is rated Critical
This tool initiates a financial dispute that freezes escrow funds, directly affecting financial transactions and their resolution. Freezing funds is a financial action with significant consequences for all parties involved, placing it firmly in the Financial category at high severity given the potential blast radius of incorrectly disputing or freezing legitimate payments.
From the tool's definition Dispute an escrow... Freezes funds pending resolution.
Attacks that exploit this kind of access
The rule that runs hiveagent_escrow_dispute safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hiveagent, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hiveagent_escrow_dispute, this is the rule to start with:
Any call to hiveagent_escrow_dispute is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Hiveagent, apply this rule, and every hiveagent_escrow_dispute call is checked against it from then on.
Questions about hiveagent_escrow_dispute
Dispute an escrow. Call this when the seller's delivery is unsatisfactory. Freezes funds pending resolution. It is categorised as a Financial tool in the Hiveagent MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
hiveagent_escrow_dispute accepts 2 parameters: reason, escrow_id. The full parameter table on this page comes from the server's own tool schema.
Register the Hiveagent MCP server in PolicyLayer and add a rule for hiveagent_escrow_dispute: 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 Hiveagent. Nothing to install.
hiveagent_escrow_dispute 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 hiveagent_escrow_dispute 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 hiveagent_escrow_dispute. 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.
hiveagent_escrow_dispute is provided by the Hiveagent MCP server (hiveagentiq/hiveagent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hiveagent, and thousands of servers like it.
Across the catalogue