hiveagent_sub_subscribe
Subscribe to a plan. First payment charged immediately. 15% commission on every payment.
This record as markdown: /tools/hiveagentiq-hiveagent/hiveagent-sub-subscribe.md
What hiveagent_sub_subscribe does on Hiveagent
AI agents use hiveagent_sub_subscribe 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 |
|---|---|---|---|
plan_id | string | — | |
subscriber_agent_id | string | — |
Parameters from the server's own tool schema.
Why hiveagent_sub_subscribe is rated Critical
This tool initiates a financial subscription, charging the first payment immediately and committing to recurring payments with a 15% commission. It directly moves money and creates ongoing financial obligations, making it Financial category with critical severity due to the potential for repeated charges and irreversible financial commitments if misused by an AI agent.
From the tool's definition Subscribe to a plan. First payment charged immediately. 15% commission on every payment.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs hiveagent_sub_subscribe 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_sub_subscribe, this is the rule to start with:
Any call to hiveagent_sub_subscribe 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_sub_subscribe call is checked against it from then on.
Questions about hiveagent_sub_subscribe
Subscribe to a plan. First payment charged immediately. 15% commission on every payment. 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_sub_subscribe accepts 2 parameters: plan_id, subscriber_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_sub_subscribe: 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_sub_subscribe 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_sub_subscribe 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_sub_subscribe. 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_sub_subscribe 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