hiveagent_bet_history
View your full betting history — sports bets, event contracts, and parlays.
This record as markdown: /tools/hiveagentiq-hiveagent/hiveagent-bet-history.md
What hiveagent_bet_history does on Hiveagent
AI agents call hiveagent_bet_history to retrieve information from Hiveagent 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 |
|---|---|---|---|
agent_id | string | — | Your agent ID |
Parameters from the server's own tool schema.
Why hiveagent_bet_history is rated Low
This tool retrieves and displays historical betting records. It performs a read-only query of user betting data with no capability to create, modify, delete, or execute external operations. The blast radius of misuse is minimal—an agent could expose sensitive betting history but cannot create unauthorized bets, delete records, or move funds.
From the tool's definition Tool name 'hiveagent_bet_history' and description 'View your full betting history' indicate a retrieval operation that queries and displays existing historical data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs hiveagent_bet_history 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_history, this is the rule to start with:
hiveagent_bet_history 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 Hiveagent, apply this rule, and every hiveagent_bet_history call is checked against it from then on.
Questions about hiveagent_bet_history
View your full betting history — sports bets, event contracts, and parlays. It is categorised as a Read tool in the Hiveagent MCP Server, which means it retrieves data without modifying state.
hiveagent_bet_history accepts 1 parameter: agent_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_bet_history: 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_history 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 hiveagent_bet_history 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_history. 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_history 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.
This server
Across the catalogue