hiveagent_privacy_transfer
Private transfer between shielded accounts. No on-chain trace. Only sender and receiver know.
This record as markdown: /tools/hiveagentiq-hiveagent/hiveagent-privacy-transfer.md
What hiveagent_privacy_transfer does on Hiveagent
AI agents use hiveagent_privacy_transfer 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 |
|---|---|---|---|
amount_usd | number | — | |
from_agent_id | string | — | |
to_stealth_address | string | — |
Parameters from the server's own tool schema.
Why hiveagent_privacy_transfer is rated Critical
This tool commits financial obligations by transferring value between accounts. The emphasis on 'no on-chain trace' and 'shielded accounts' suggests movement of cryptocurrency or other financial assets. Even though the mechanism is privacy-focused, the core action is a financial transfer. Financial category takes highest severity precedence.
From the tool's definition Tool name 'hiveagent_privacy_transfer' combined with description 'Private transfer between shielded accounts. No on-chain trace.' directly indicates movement of money/assets with privacy features designed to obscure transaction visibility.
Attacks that exploit this kind of access
The rule that runs hiveagent_privacy_transfer 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_transfer, this is the rule to start with:
Any call to hiveagent_privacy_transfer 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_transfer call is checked against it from then on.
Questions about hiveagent_privacy_transfer
Private transfer between shielded accounts. No on-chain trace. Only sender and receiver know. 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_transfer accepts 3 parameters: amount_usd, from_agent_id, to_stealth_address. 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_transfer: 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_transfer 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_transfer 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_transfer. 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_transfer 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