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 ...
AI agents call getRfqConfig to retrieve information from Bybit MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
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.
Documented attack patterns abuse exactly the kind of access getRfqConfig gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bybit MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for getRfqConfig:
{
"version": "1",
"default": "deny",
"tools": {
"getRfqConfig": {}
}
}getRfqConfig is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
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.
Start from Bybit MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
326 Bybit MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.