This record as markdown: /tools/instantkom-mcp-server/subscribe-to-plan.md
What subscribe_to_plan does on instantKOM MCP Server
AI agents use subscribe_to_plan to commit financial operations through instantKOM MCP Server, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why subscribe_to_plan is rated Critical
Subscribing to a plan directly creates a financial commitment, such as recurring payments or billing. This falls squarely in the Financial category, which is the most severe. Misuse could result in unauthorized charges or subscriptions.
From the tool's definition 'Subscribe to a plan' - subscribing to a plan commits a financial obligation on behalf of the user
Attacks that exploit this kind of access
The rule that runs subscribe_to_plan safely
PolicyLayer is an MCP gateway: it sits between your AI agents and instantKOM MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For subscribe_to_plan, this is the rule to start with:
Any call to subscribe_to_plan is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect instantKOM MCP Server, apply this rule, and every subscribe_to_plan call is checked against it from then on.
Questions about subscribe_to_plan
Subscribe to a plan. It is categorised as a Financial tool in the instantKOM MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the instantKOM MCP Server MCP server in PolicyLayer and add a rule for subscribe_to_plan: 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 instantKOM MCP Server. Nothing to install.
subscribe_to_plan 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 subscribe_to_plan 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 subscribe_to_plan. 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.
subscribe_to_plan is provided by the instantKOM MCP Server MCP server (instantkom/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on instantKOM MCP Server, and thousands of servers like it.
Across the catalogue