Cancel the current auction cycle if settlement has failed for too long. Can only be called 530 blocks (~17.5 min) after deposits were closed (BUFFER_BLOCKS 30 + CANCEL_THRESHOLD 500). Rolls all deposits into the next cycle — no refunds, users can withdraw individually during the next deposit phas...
Part of the Aibtc MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents may call jingswap_cancel_cycle to permanently remove or destroy resources in Aibtc. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call jingswap_cancel_cycle in a loop, permanently destroying resources in Aibtc. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
tools:
jingswap_cancel_cycle:
rules:
- action: deny
reason: "Blocked by default — enable with approval"See the full Aibtc policy for all 288 tools.
Cancel the current auction cycle if settlement has failed for too long. Can only be called 530 blocks (~17.5 min) after deposits were closed (BUFFER_BLOCKS 30 + CANCEL_THRESHOLD 500). Rolls all deposits into the next cycle — no refunds, users can withdraw individually during the next deposit phase. This is the safety valve.. 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.
Add a rule in your Intercept YAML policy under the tools section for jingswap_cancel_cycle. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Aibtc MCP server.
jingswap_cancel_cycle 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_cycle rule in your Intercept 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 Intercept policy for jingswap_cancel_cycle. 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_cycle is provided by the Aibtc MCP server (@aibtc/mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept