hiveagent_privacy_deposit
Deposit funds into your shielded account. Public balance → private balance. 1% privacy fee.
This record as markdown: /tools/hiveagentiq-hiveagent/hiveagent-privacy-deposit.md
What hiveagent_privacy_deposit does on Hiveagent
AI agents use hiveagent_privacy_deposit to commit financial operations through Hiveagent, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
agent_id | string | — | |
amount_usd | number | — |
Parameters from the server's own tool schema.
Why hiveagent_privacy_deposit is rated Critical
This tool directly moves funds from a public balance to a private/shielded account, which constitutes a financial transaction. Even though it appears to be a legitimate privacy feature with a disclosed fee, an AI agent misusing this could transfer user funds without authorization, resulting in unauthorized financial movement and potential loss of funds.
From the tool's definition Tool name contains 'deposit' and description explicitly states 'Deposit funds into your shielded account' with mention of '1% privacy fee', indicating movement of money and financial obligation.
Attacks that exploit this kind of access
The rule that runs hiveagent_privacy_deposit 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_privacy_deposit, this is the rule to start with:
Any call to hiveagent_privacy_deposit is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Hiveagent, apply this rule, and every hiveagent_privacy_deposit call is checked against it from then on.
Questions about hiveagent_privacy_deposit
Deposit funds into your shielded account. Public balance → private balance. 1% privacy fee. It is categorised as a Financial tool in the Hiveagent MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
hiveagent_privacy_deposit accepts 2 parameters: agent_id, amount_usd. 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_privacy_deposit: 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_privacy_deposit is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the hiveagent_privacy_deposit 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_privacy_deposit. 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_privacy_deposit 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.
Across the catalogue