getBizTokenDetails
Query detailed information for a specific on-chain token.\nReturns project description, social links (Twitter, website, whitepaper), risk flag,\norder quantity limits, and token status.\n\nAI agent should call this when user asks about a specific token
This record as markdown: /tools/bybit-exchange-trading-mcp/getbiztokendetails.md
What getBizTokenDetails does on Bybit MCP Server
AI agents call getBizTokenDetails to retrieve information from Bybit MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why getBizTokenDetails is rated Low
This tool queries and retrieves information about tokens without creating, modifying, or destroying any data. It is a passive read operation that returns informational fields like descriptions, links, risk flags, and status. No financial transactions, code execution, or data mutation occurs.
From the tool's definition Tool name 'getBizTokenDetails' and description 'Query detailed information for a specific on-chain token' with 'Returns project description, social links, risk flag, order quantity limits, and token status' indicates retrieval of read-only data with no side…
Attacks that exploit this kind of access
The rule that runs getBizTokenDetails safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Bybit MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getBizTokenDetails, this is the rule to start with:
getBizTokenDetails 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 MCP Server, apply this rule, and every getBizTokenDetails call is checked against it from then on.
Questions about getBizTokenDetails
Query detailed information for a specific on-chain token.\nReturns project description, social links (Twitter, website, whitepaper), risk flag,\norder quantity limits, and token status.\n\nAI agent should call this when user asks about a specific token. 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 getBizTokenDetails: 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.
getBizTokenDetails 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 getBizTokenDetails 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 getBizTokenDetails. 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.
getBizTokenDetails 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.
More on Bybit MCP Server, and thousands of servers like it.
This server
Across the catalogue