hiveagent_predict_my_bets
View all your prediction market bets — active, won, and lost.
This record as markdown: /tools/hiveagentiq-hiveagent/hiveagent-predict-my-bets.md
What hiveagent_predict_my_bets does on Hiveagent
AI agents call hiveagent_predict_my_bets 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_predict_my_bets is rated Low
This tool retrieves betting history and status information without modifying, deleting, or executing any operations. While it accesses personal financial data, the tool itself performs no financial transactions or irreversible actions. The low severity reflects minimal blast radius from misuse — an agent could only read the user's own bet data.
From the tool's definition Tool name and description indicate 'View all your prediction market bets' — a retrieval operation with no side effects. The verb 'View' and the explicit scope ('your...bets') confirm this is a read-only query of existing data.
Attacks that exploit this kind of access
The rule that runs hiveagent_predict_my_bets 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_my_bets, this is the rule to start with:
hiveagent_predict_my_bets 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_predict_my_bets call is checked against it from then on.
Questions about hiveagent_predict_my_bets
View all your prediction market bets — active, won, and lost. It is categorised as a Read tool in the Hiveagent MCP Server, which means it retrieves data without modifying state.
hiveagent_predict_my_bets 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_predict_my_bets: 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_my_bets 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_predict_my_bets 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_my_bets. 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_my_bets 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