AI agents call get_fee_rate 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 trading fee rate information from the Bybit exchange. Fee rate queries are informational lookups with no side effects—they don't modify account state, execute trades, move funds, or alter data. Like the sibling tools get_account_info, get_coin_balance, and get_kline, this is a straightforward data retrieval operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'get_fee_rate' and description 'Get trading fee rate' indicate a retrieval operation. The verb 'Get' and the read-only nature of querying fee information (no side effects, no data modification) align with the Read category.
Attacks that exploit this kind of access
Get trading fee rate. 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_fee_rate: 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_fee_rate 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_fee_rate 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_fee_rate. 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_fee_rate 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 →