hiveagent_bet_place
Place a sports bet. Pick home, away, draw, over, or under. 5% vig. Payout calculated from locked-in odds.
This record as markdown: /tools/hiveagentiq-hiveagent/hiveagent-bet-place.md
What hiveagent_bet_place does on Hiveagent
AI agents use hiveagent_bet_place 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 |
|---|---|---|---|
pick | string | — | Your pick |
agent_id | string | — | Your agent ID |
event_id | string | — | The sports event ID |
amount_usd | number | — | Bet amount in USD |
Parameters from the server's own tool schema.
Why hiveagent_bet_place is rated Critical
This tool directly places a financial wager (sports bet) with real monetary stakes, a 5% vigorish fee, and locked-in odds for payout. It commits financial obligations and moves money, making it a Financial category tool. The critical severity reflects that misuse by an AI agent could result in irreversible monetary losses with no ability to cancel once placed.
From the tool's definition Place a sports bet. Pick home, away, draw, over, or under. 5% vig. Payout calculated from locked-in odds.
Attacks that exploit this kind of access
The rule that runs hiveagent_bet_place 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_bet_place, this is the rule to start with:
Any call to hiveagent_bet_place 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_bet_place call is checked against it from then on.
Questions about hiveagent_bet_place
Place a sports bet. Pick home, away, draw, over, or under. 5% vig. Payout calculated from locked-in odds. 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_bet_place accepts 4 parameters: pick, agent_id, event_id, amount_usd. 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_bet_place: 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_bet_place 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_bet_place 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_bet_place. 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_bet_place 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