Create a new Request for Quote (RFQ) to solicit pricing from selected counterparties.\nThe inquirer specifies one or more legs (instruments) and a list of counterparties to receive the RFQ.\nEach leg defines a product category, symbol, direction, and quantity.\n\nRate Limit: 50 requests per secon...
AI agents use createRfq to create or update resources in Bybit MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bybit MCP Server environment.
This tool creates a new RFQ, which is a reversible write operation that generates a new record/request in the trading system. While it initiates a financial interaction, it does not directly move money or execute trades; it solicits quotes. The Write category is appropriate as it creates new data structures.
From the tool's definition Tool description states 'Create a new Request for Quote (RFQ)' and specifies that 'The inquirer specifies one or more legs (instruments) and a list of counterparties to receive the RFQ.' This creates a new financial instrument request that modifies state on…
Documented attack patterns abuse exactly the kind of access createRfq 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 createRfq:
{
"version": "1",
"default": "deny",
"tools": {
"createRfq": {
"limits": [
{
"counter": "createrfq_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}createRfq stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new Request for Quote (RFQ) to solicit pricing from selected counterparties.\nThe inquirer specifies one or more legs (instruments) and a list of counterparties to receive the RFQ.\nEach leg defines a product category, symbol, direction, and quantity.\n\nRate Limit: 50 requests per second.\n\nTip: Use the Get RFQ Config endpoint to retrieve available counterparties, strategy types,\nand maximum leg count before creating an RFQ.\n\nAgent hint: Use this endpoint to create a new RFQ. You must first call Get RFQ Config to obtain valid\ncounterparty deskCodes and the maximum number of legs allowed. All legs must share the same\nbase and settlement coins. It is categorised as a Write tool in the Bybit MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bybit MCP Server MCP server in PolicyLayer and add a rule for createRfq: 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.
createRfq is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the createRfq 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 createRfq. 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.
createRfq 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.