getRfqConfig
Retrieve the RFQ configuration for the authenticated account, including available counterparties,\nstrategy types, maximum legs, and minimum order quantities.\n\nRate Limit: 50 requests per second.\n\nTip: Call this endpoint before creating an RFQ to obtain valid counterparty deskCodes,\nallowed ...
This record as markdown: /tools/bybit-exchange-trading-mcp/getrfqconfig.md
What getRfqConfig does on Bybit MCP Server
AI agents call getRfqConfig 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 getRfqConfig is rated Low
This tool performs a read-only query of RFQ configuration metadata for the authenticated account. It retrieves data about available options and limits without creating, modifying, or executing any trades or financial transactions. The low severity reflects that misuse would only expose configuration information already accessible to the authenticated account holder.
From the tool's definition Tool description states 'Retrieve the RFQ configuration' with no modification, deletion, or execution of external operations. It queries account settings and configuration data (counterparties, strategy types, limits) and returns information only.
Attacks that exploit this kind of access
The rule that runs getRfqConfig 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 getRfqConfig, this is the rule to start with:
getRfqConfig 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 getRfqConfig call is checked against it from then on.
Questions about getRfqConfig
Retrieve the RFQ configuration for the authenticated account, including available counterparties,\nstrategy types, maximum legs, and minimum order quantities.\n\nRate Limit: 50 requests per second.\n\nTip: Call this endpoint before creating an RFQ to obtain valid counterparty deskCodes,\nallowed strategy types, and trading limits.\n\nAgent hint: Call this endpoint first to discover your deskCode, available counterparties, strategy types,\nand trading limits before creating RFQs or quotes. 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 getRfqConfig: 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.
getRfqConfig 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 getRfqConfig 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 getRfqConfig. 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.
getRfqConfig 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