get_transferable_coin
Get transferable coins between account types.
This record as markdown: /tools/johnnywic-bybit-mcp/get-transferable-coin.md
What get_transferable_coin does on Bybit
AI agents call get_transferable_coin to retrieve information from Bybit without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_transferable_coin is rated Low
This tool queries account metadata to determine which coins can be transferred between account types. It is a passive information retrieval operation with no side effects on funds, positions, or account state. No financial transactions are initiated, no data is modified, and no external operations are triggered.
From the tool's definition Tool name and description indicate retrieval of information: 'Get transferable coins between account types.' No mutation, deletion, or execution of trades/commands occurs.
Attacks that exploit this kind of access
The rule that runs get_transferable_coin 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 get_transferable_coin, this is the rule to start with:
get_transferable_coin is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Bybit, apply this rule, and every get_transferable_coin call is checked against it from then on.
Questions about get_transferable_coin
Get transferable coins between account types. It is categorised as a Read tool in the Bybit MCP Server, which means it retrieves data without modifying state.
Register the Bybit MCP server in PolicyLayer and add a rule for get_transferable_coin: 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.
get_transferable_coin 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 get_transferable_coin 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 get_transferable_coin. 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.
get_transferable_coin 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.
More on Bybit, and thousands of servers like it.
This server
Across the catalogue