Cancel a pending withdrawal.
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.
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
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.
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.
cancel_withdrawal 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 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.
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.
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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →