stackspot_cancel_pot
Cancel a Stackspot stacking lottery pot before stacking begins. Cancels an unlocked pot to recover contributed STX. The pot must not yet be locked (i.e., stacking has not started). Once stacking begins the pot cannot be cancelled. Use a bare contract name (e.g.,
This record as markdown: /tools/io-github-aibtcdev-mcp-server/stackspot-cancel-pot.md
What stackspot_cancel_pot does on Aibtc
AI agents call stackspot_cancel_pot to permanently remove resources in Aibtc, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why stackspot_cancel_pot is rated Critical
This tool destroys the state of a stacking pot by cancelling it, which is an irreversible operation. Even though funds are recovered, the pot itself is destroyed and cannot be reused once cancelled. The action cannot be undone after execution. While it involves financial assets (STX), the primary destructive nature of cancellation (rather than mere fund transfer) makes Destructive the most appropriate category.
From the tool's definition 'Cancel a Stackspot stacking lottery pot' and 'Cancels an unlocked pot to recover contributed STX' — this irreversibly cancels a pot and recovers funds, preventing future stacking operations on that pot.
Attacks that exploit this kind of access
The rule that runs stackspot_cancel_pot safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aibtc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For stackspot_cancel_pot, this is the rule to start with:
stackspot_cancel_pot is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every stackspot_cancel_pot call is checked against it from then on.
Questions about stackspot_cancel_pot
Cancel a Stackspot stacking lottery pot before stacking begins. Cancels an unlocked pot to recover contributed STX. The pot must not yet be locked (i.e., stacking has not started). Once stacking begins the pot cannot be cancelled. Use a bare contract name (e.g.,. It is categorised as a Destructive tool in the Aibtc MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Aibtc MCP server in PolicyLayer and add a rule for stackspot_cancel_pot: 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 Aibtc. Nothing to install.
stackspot_cancel_pot is a Destructive 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 stackspot_cancel_pot 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 stackspot_cancel_pot. 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.
stackspot_cancel_pot is provided by the Aibtc MCP server (aibtcdev/aibtc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aibtc, and thousands of servers like it.
Across the catalogue