AI agents use withdraw to commit financial operations through Bybit — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool directly moves financial assets (cryptocurrency) out of the user's Bybit account to an external address. This is a Financial operation with critical severity due to the irreversible nature of blockchain transactions, potential for total loss of funds if the wrong address is specified, and the high-value impact of unauthorized withdrawals.
From the tool's definition Tool name 'withdraw' and description 'Withdraw funds to an external address' indicate irreversible movement of money from the user's account to an external cryptocurrency address.
Attacks that exploit this kind of access
Withdraw funds to an external address. It is categorised as a Financial tool in the Bybit MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Bybit MCP server in PolicyLayer and add a rule for withdraw: 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.
withdraw is a Financial 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 withdraw 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 withdraw. 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.
withdraw 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 →