This record as markdown: /tools/johnnywic-bybit-mcp/create-rfq.md
What create_rfq does on Bybit
AI agents use create_rfq to create or update resources in Bybit, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bybit environment.
Why create_rfq is rated Medium
Creating an RFQ is a reversible write operation that initiates a financial transaction request on a trading exchange. While it doesn't execute trades or move funds directly (which would be Execute or Financial), it creates a binding or semi-binding request that could commit the user to financial obligations depending on quote acceptance.
From the tool's definition Tool name 'create_rfq' and description 'Create an RFQ (Request for Quote)' indicates creation of a financial instrument request.
Attacks that exploit this kind of access
The rule that runs create_rfq 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 create_rfq, this is the rule to start with:
create_rfq 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Bybit, apply this rule, and every create_rfq call is checked against it from then on.
Questions about create_rfq
Create an RFQ (Request for Quote). It is categorised as a Write tool in the Bybit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bybit MCP server in PolicyLayer and add a rule for create_rfq: 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.
create_rfq 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 create_rfq 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 create_rfq. 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.
create_rfq 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.
More on Bybit, and thousands of servers like it.
This server
Across the catalogue