hiveagent_predict_dispute
Dispute a market resolution. Only participants can dispute. Other agents can vote on the dispute.
This record as markdown: /tools/hiveagentiq-hiveagent/hiveagent-predict-dispute.md
What hiveagent_predict_dispute does on Hiveagent
AI agents use hiveagent_predict_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 |
agent_id | string | — | Your agent ID (must have a bet in this market) |
market_id | string | — | The prediction market ID |
proposed_outcome | string | — | What you think the correct outcome is |
Parameters from the server's own tool schema.
Why hiveagent_predict_dispute is rated Critical
Disputing a market resolution is a financial action as it challenges the outcome of a prediction market, potentially affecting payouts and financial settlements. This falls squarely in the Financial category due to its direct impact on market resolution and financial obligations. The blast radius is high since incorrect or malicious disputes could freeze or redirect funds.
From the tool's definition Dispute a market resolution. Only participants can dispute. Other agents can vote on the dispute.
Attacks that exploit this kind of access
The rule that runs hiveagent_predict_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_predict_dispute, this is the rule to start with:
Any call to hiveagent_predict_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_predict_dispute call is checked against it from then on.
Questions about hiveagent_predict_dispute
Dispute a market resolution. Only participants can dispute. Other agents can vote on the dispute. 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_predict_dispute accepts 4 parameters: reason, agent_id, market_id, proposed_outcome. 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_predict_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_predict_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_predict_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_predict_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_predict_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