cancel_withdrawal

Cancel a pending withdrawal.

SERVERBybit SOURCEjohnnywic/bybit-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/johnnywic-bybit-mcp/cancel-withdrawal.md

WHAT IT DOES

What cancel_withdrawal does on Bybit

AI agents call cancel_withdrawal to permanently remove resources in Bybit, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why cancel_withdrawal is rated Critical

While not technically deleting data, canceling a withdrawal is a destructive action that irreversibly undoes a financial operation. The user's intent to move funds is permanently negated without possibility of restoration through this tool alone. Combined with the Bybit trading context (financial exchange), this carries high blast radius if triggered erroneously on a large pending withdrawal.

From the tool's definition 'Cancel a pending withdrawal' - this action irreversibly cancels a financial transaction that was in progress, preventing funds from being transferred out of the account.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs cancel_withdrawal safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Bybit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cancel_withdrawal, this is the rule to start with:

cancel_withdrawal Hidden

cancel_withdrawal is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "cancel_withdrawal"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Bybit, apply this rule, and every cancel_withdrawal call is checked against it from then on.

FAQ

Questions about cancel_withdrawal

What does the cancel_withdrawal tool do? +

Cancel a pending withdrawal. It is categorised as a Destructive tool in the Bybit MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on cancel_withdrawal? +

Register the Bybit MCP server in PolicyLayer and add a rule for cancel_withdrawal: 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 Bybit. Nothing to install.

What risk level is cancel_withdrawal? +

cancel_withdrawal is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit cancel_withdrawal? +

Yes. Add a rate_limit block to the cancel_withdrawal 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.

How do I block cancel_withdrawal completely? +

Set action: deny in the PolicyLayer policy for cancel_withdrawal. 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.

What MCP server provides cancel_withdrawal? +

cancel_withdrawal is provided by the Bybit MCP server (johnnywic/bybit-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Bybit, and thousands of servers like it.

This server

All 245 Bybit tools → Critical-risk tools on this server →

Across the catalogue

sms_cancel_scheduled on Twilio SMS MCP Server →cancel_all_orders on Lighter MCP → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →