cancel_all_rfqs

Cancel all open RFQs.

SERVERBybit SOURCEjohnnywic/bybit-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/johnnywic-bybit-mcp/cancel-all-rfqs.md

WHAT IT DOES

What cancel_all_rfqs does on Bybit

AI agents call cancel_all_rfqs to permanently remove resources in Bybit, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why cancel_all_rfqs is rated Critical

Cancelling all open RFQs is a bulk irreversible action that terminates active trading requests. While it doesn't delete data permanently, mass-cancelling all open RFQs cannot be undone and could disrupt active trading workflows significantly. This falls under Destructive due to its irreversible bulk nature, with high severity given the potential blast radius of cancelling all active quote requests simultaneously.

From the tool's definition Cancel all open RFQs — mass cancellation of all open Request for Quote orders, which is irreversible

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs cancel_all_rfqs safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Bybit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cancel_all_rfqs, this is the rule to start with:

cancel_all_rfqs Hidden

cancel_all_rfqs is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "cancel_all_rfqs"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Bybit, apply this rule, and every cancel_all_rfqs call is checked against it from then on.

FAQ

Questions about cancel_all_rfqs

What does the cancel_all_rfqs tool do? +

Cancel all open RFQs. It is categorised as a Destructive tool in the Bybit MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on cancel_all_rfqs? +

Register the Bybit MCP server in PolicyLayer and add a rule for cancel_all_rfqs: 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. Nothing to install.

What risk level is cancel_all_rfqs? +

cancel_all_rfqs is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit cancel_all_rfqs? +

Yes. Add a rate_limit block to the cancel_all_rfqs 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.

How do I block cancel_all_rfqs completely? +

Set action: deny in the PolicyLayer policy for cancel_all_rfqs. 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.

What MCP server provides cancel_all_rfqs? +

cancel_all_rfqs is provided by the Bybit MCP server (johnnywic/bybit-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Bybit, and thousands of servers like it.

This server

All 245 Bybit tools → Critical-risk tools on this server →

Across the catalogue

cancel_all_orders on Lighter MCP →sms_cancel_scheduled on Twilio SMS MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →