cancelRfq
Cancel an active RFQ. You must pass either
This record as markdown: /tools/bybit-exchange-trading-mcp/cancelrfq.md
What cancelRfq does on Bybit MCP Server
AI agents call cancelRfq 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 cancelRfq is rated Critical
Cancelling an active RFQ is an irreversible action in the trading workflow. Once cancelled, the RFQ (Request for Quote) cannot be restored, making this a Destructive operation. The blast radius is high because it could disrupt active trading negotiations or hedging strategies on the Bybit exchange.
From the tool's definition Cancel an active RFQ — cancellation of a trading request-for-quote is irreversible; the RFQ cannot be reinstated once cancelled.
Attacks that exploit this kind of access
The rule that runs cancelRfq 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 cancelRfq, this is the rule to start with:
cancelRfq 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 cancelRfq call is checked against it from then on.
Questions about cancelRfq
Cancel an active RFQ. You must pass either. 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 cancelRfq: 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.
cancelRfq 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 cancelRfq 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 cancelRfq. 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.
cancelRfq 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