cancel_instance
Cancel your subscription and deactivate one private subscribed instance.
This record as markdown: /tools/io-github-proagentstore-platform/cancel-instance.md
What cancel_instance does on ProAgentStore
AI agents use cancel_instance to commit financial operations through ProAgentStore, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why cancel_instance is rated Critical
This tool cancels a subscription, which is a financial action (terminating a financial commitment/obligation). It also deactivates an instance, making it potentially destructive/irreversible. Financial is the highest severity category and applies here since a subscription cancellation directly affects billing and financial commitments.
From the tool's definition Cancel your subscription and deactivate one private subscribed instance
Attacks that exploit this kind of access
The rule that runs cancel_instance safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ProAgentStore, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cancel_instance, this is the rule to start with:
Any call to cancel_instance is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect ProAgentStore, apply this rule, and every cancel_instance call is checked against it from then on.
Questions about cancel_instance
Cancel your subscription and deactivate one private subscribed instance. It is categorised as a Financial tool in the ProAgentStore MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the ProAgentStore MCP server in PolicyLayer and add a rule for cancel_instance: 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 ProAgentStore. Nothing to install.
cancel_instance 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 cancel_instance 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 cancel_instance. 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.
cancel_instance is provided by the ProAgentStore MCP server (https://mcp.proagentstore.online/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ProAgentStore, and thousands of servers like it.
Across the catalogue