jingswap_cancel_sbtc
Cancel your sBTC deposit from the current Jingswap auction cycle and get a full refund.
This record as markdown: /tools/io-github-aibtcdev-mcp-server/jingswap-cancel-sbtc.md
What jingswap_cancel_sbtc does on Aibtc
AI agents call jingswap_cancel_sbtc 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 jingswap_cancel_sbtc is rated Critical
The tool cancels a deposit, which is a destructive action that changes the state of a financial position irreversibly. Although it results in a refund (a positive outcome), the cancellation itself is an operation that cannot be undone once executed—the user's participation in the auction cycle is terminated.
From the tool's definition Tool name 'cancel' and description 'Cancel your sBTC deposit...and get a full refund' indicate an irreversible state change to a financial deposit/auction participation.
Attacks that exploit this kind of access
The rule that runs jingswap_cancel_sbtc 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 jingswap_cancel_sbtc, this is the rule to start with:
jingswap_cancel_sbtc 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 jingswap_cancel_sbtc call is checked against it from then on.
Questions about jingswap_cancel_sbtc
Cancel your sBTC deposit from the current Jingswap auction cycle and get a full refund. 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 jingswap_cancel_sbtc: 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.
jingswap_cancel_sbtc 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 jingswap_cancel_sbtc 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 jingswap_cancel_sbtc. 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.
jingswap_cancel_sbtc 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