getFeeRate
Query the maker and taker fee rates for the specified product category.\nCan filter by symbol (spot/linear/inverse) or baseCoin (options only).\n\nRate limit: 10 req/s\n\nAgent hint: Use this to check fee rates before trading. The category parameter is required.\nUse symbol to filter for spot/lin...
This record as markdown: /tools/bybit-exchange-trading-mcp/getfeerate.md
What getFeeRate does on Bybit MCP Server
AI agents call getFeeRate 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 getFeeRate is rated Low
This tool retrieves fee rate information from the Bybit exchange. It is a read-only operation that queries existing data without side effects. The rate limit (10 req/s) and agent hint to 'check fee rates before trading' confirm this is informational. Even though it relates to a financial exchange, the tool itself only reads data and does not move money, execute trades, or commit financial obligations.
From the tool's definition Query the maker and taker fee rates for the specified product category. Tool name 'getFeeRate' and description indicate data retrieval with 'query' and 'check' — no creation, modification, or deletion of data.
Attacks that exploit this kind of access
The rule that runs getFeeRate 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 getFeeRate, this is the rule to start with:
getFeeRate 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 getFeeRate call is checked against it from then on.
Questions about getFeeRate
Query the maker and taker fee rates for the specified product category.\nCan filter by symbol (spot/linear/inverse) or baseCoin (options only).\n\nRate limit: 10 req/s\n\nAgent hint: Use this to check fee rates before trading. The category parameter is required.\nUse symbol to filter for spot/linear/inverse. Use baseCoin for options (e.g., BTC, ETH, SOL).\nFee rates are returned as decimal strings (e.g., \. 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 getFeeRate: 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.
getFeeRate 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 getFeeRate 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 getFeeRate. 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.
getFeeRate 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