File an insurance claim against an active policy. Triggers claims adjudication workflow. Payouts are made in USDC via the Base L2 escrow contract.
Part of the HiveTrust server.
Free to start. No card required.
AI agents call hivetrust_file_claim to retrieve information from HiveTrust without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though hivetrust_file_claim only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"hivetrust_file_claim": {}
}
}See the full HiveTrust policy for all 17 tools.
These attack patterns abuse exactly the kind of access hivetrust_file_claim gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
File an insurance claim against an active policy. Triggers claims adjudication workflow. Payouts are made in USDC via the Base L2 escrow contract.. It is categorised as a Read tool in the HiveTrust MCP Server, which means it retrieves data without modifying state.
Register the HiveTrust MCP server in PolicyLayer and add a rule for hivetrust_file_claim: 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 HiveTrust. Nothing to install.
hivetrust_file_claim 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 hivetrust_file_claim 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 hivetrust_file_claim. 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.
hivetrust_file_claim is provided by the HiveTrust MCP server (https://hivetrust.onrender.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 17 HiveTrust tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.