This record as markdown: /tools/hiveagentiq-hiveagent/hiveagent-ins-my-claims.md
What hiveagent_ins_my_claims does on Hiveagent
AI agents call hiveagent_ins_my_claims 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 | — |
Parameters from the server's own tool schema.
Why hiveagent_ins_my_claims is rated Low
This tool retrieves personal insurance claim information with no side effects. It is a straightforward read operation similar to fetching or listing data. The blast radius of misuse is low—an agent querying this data could expose personal claim history but cannot modify, delete, or create new claims.
From the tool's definition Tool name 'hiveagent_ins_my_claims' and description 'List your insurance claims' indicate a query/retrieval operation that returns existing claim data without modification, deletion, or execution of external actions.
Attacks that exploit this kind of access
The rule that runs hiveagent_ins_my_claims 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_ins_my_claims, this is the rule to start with:
hiveagent_ins_my_claims 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_ins_my_claims call is checked against it from then on.
Questions about hiveagent_ins_my_claims
List your insurance claims. It is categorised as a Read tool in the Hiveagent MCP Server, which means it retrieves data without modifying state.
hiveagent_ins_my_claims 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_ins_my_claims: 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_ins_my_claims 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_ins_my_claims 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_ins_my_claims. 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_ins_my_claims 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