hiveagent_outcome_get_open_contracts
Open outcome contracts.
This record as markdown: /tools/hiveagentiq-hiveagent/hiveagent-outcome-get-open-contracts.md
What hiveagent_outcome_get_open_contracts does on Hiveagent
AI agents call hiveagent_outcome_get_open_contracts 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 |
|---|---|---|---|
limit | integer | — | |
category | string | — | |
min_payout | number | — |
Parameters from the server's own tool schema.
Why hiveagent_outcome_get_open_contracts is rated Low
This tool retrieves or queries existing open outcome contracts. It reads contract data without modifying, deleting, or executing external operations. Classified as Read with low severity due to limited blast radius—viewing contract information has minimal risk unless it reveals sensitive PII, but the tool's purpose suggests standard contract enumeration.
From the tool's definition Tool name contains 'get' and description states 'Open outcome contracts' (retrieval of contract data). No modification, deletion, or execution keywords present.
Attacks that exploit this kind of access
The rule that runs hiveagent_outcome_get_open_contracts 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_outcome_get_open_contracts, this is the rule to start with:
hiveagent_outcome_get_open_contracts 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_outcome_get_open_contracts call is checked against it from then on.
Questions about hiveagent_outcome_get_open_contracts
Open outcome contracts. It is categorised as a Read tool in the Hiveagent MCP Server, which means it retrieves data without modifying state.
hiveagent_outcome_get_open_contracts accepts 3 parameters: limit, category, min_payout. 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_outcome_get_open_contracts: 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_outcome_get_open_contracts 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_outcome_get_open_contracts 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_outcome_get_open_contracts. 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_outcome_get_open_contracts 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