AI agents call get_coin_info to retrieve information from Bybit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves static or quasi-static cryptocurrency metadata (chain information, deposit/withdrawal availability status) without modifying any data, executing code, or affecting account state. It is a standard informational query typical of exchange APIs. Classification as Read is appropriate; severity is low because misuse carries minimal risk—the information is intended to be public or user-accessible.
From the tool's definition Tool name 'get_coin_info' and description 'Query coin information including chain info, deposit/withdraw status' indicate a retrieval operation with no side effects. The verb 'Query' and the use of 'get_' prefix confirm read-only semantics.
Attacks that exploit this kind of access
Query coin information including chain info, deposit/withdraw status. 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_coin_info: 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_coin_info 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_coin_info 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_coin_info. 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_coin_info is provided by the Bybit MCP server (workspace/bybit-mcp-server). 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 →