cancelAllRfqs
Cancel all active RFQs for the authenticated account.\nReturns an array of cancellation results, one per RFQ.\nWhen an inquirer cancels, all corresponding quotes become invalid.\nWhen a quoter cancels, the inquiry remains unaffected but the quote becomes invalid.\n\nRate Limit: 50 requests per se...
This record as markdown: /tools/bybit-exchange-trading-mcp/cancelallrfqs.md
What cancelAllRfqs does on Bybit MCP Server
AI agents call cancelAllRfqs to permanently remove resources in Bybit MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why cancelAllRfqs is rated Critical
This tool irreversibly cancels all active RFQs (Requests for Quotes) simultaneously. Cancellation of RFQs invalidates associated quotes, which cannot be undone. The bulk nature ('all active RFQs at once') amplifies the blast radius significantly, making misuse potentially highly disruptive to active trading operations.
From the tool's definition Cancel all active RFQs... cancels all active RFQs at once... all corresponding quotes become invalid
Attacks that exploit this kind of access
The rule that runs cancelAllRfqs 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 cancelAllRfqs, this is the rule to start with:
cancelAllRfqs is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Bybit MCP Server, apply this rule, and every cancelAllRfqs call is checked against it from then on.
Questions about cancelAllRfqs
Cancel all active RFQs for the authenticated account.\nReturns an array of cancellation results, one per RFQ.\nWhen an inquirer cancels, all corresponding quotes become invalid.\nWhen a quoter cancels, the inquiry remains unaffected but the quote becomes invalid.\n\nRate Limit: 50 requests per second.\n\nAgent hint: This endpoint cancels all active RFQs at once. No request body is needed.\nThe response returns an array of results showing which RFQs were cancelled. It is categorised as a Destructive tool in the Bybit MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Bybit MCP Server MCP server in PolicyLayer and add a rule for cancelAllRfqs: 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.
cancelAllRfqs is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the cancelAllRfqs 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 cancelAllRfqs. 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.
cancelAllRfqs 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.
Across the catalogue