Get the withdrawable amount for a specific coin across different account types.\n- Returns withdrawable amounts for FUND and UTA accounts.\n- Funds may be partially frozen due to on-chain deposits awaiting confirmations or risk review.\n tags:\n- Asset
AI agents call getWithdrawableAmountByCoin to retrieve information from Bybit MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries account asset information and returns withdrawable amounts. It performs no mutations, does not execute operations, does not delete data, and does not move funds. The 'get' verb and read-only nature (retrieving current account state) confirm it is a Read operation.
From the tool's definition Tool name 'getWithdrawableAmountByCoin' and description 'Get the withdrawable amount for a specific coin' clearly indicate a read operation that retrieves account balance information without modifying data.
Documented attack patterns abuse exactly the kind of access getWithdrawableAmountByCoin gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bybit MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for getWithdrawableAmountByCoin:
{
"version": "1",
"default": "deny",
"tools": {
"getWithdrawableAmountByCoin": {}
}
}getWithdrawableAmountByCoin is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the withdrawable amount for a specific coin across different account types.\n- Returns withdrawable amounts for FUND and UTA accounts.\n- Funds may be partially frozen due to on-chain deposits awaiting confirmations or risk review.\n tags:\n- Asset. It is categorised as a Read tool in the Bybit MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Bybit MCP Server MCP server in PolicyLayer and add a rule for getWithdrawableAmountByCoin: 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 MCP Server. Nothing to install.
getWithdrawableAmountByCoin is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the getWithdrawableAmountByCoin 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 getWithdrawableAmountByCoin. 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.
getWithdrawableAmountByCoin is provided by the Bybit MCP Server MCP server (bybit-exchange/trading-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Bybit MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
326 Bybit MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.