Enable acceptance of non-LP quotes for a specific RFQ.\nThis allows the inquirer to receive and execute quotes from normal counterparties\nin addition to liquidity providers.\n\nRate Limit: 50 requests per second.\n\nAgent hint: Use this endpoint to allow non-LP counterparties to quote on your RF...
AI agents invoke acceptNonLpQuote to trigger actions in Bybit MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool modifies the execution rules of an active RFQ (Request for Quote) on a cryptocurrency exchange, enabling quotes from non-LP counterparties to be executed. It triggers an external operation on the exchange that changes trading behavior for live orders.
From the tool's definition Enable acceptance of non-LP quotes for a specific RFQ... allows the inquirer to receive and execute quotes from normal counterparties
Documented attack patterns abuse exactly the kind of access acceptNonLpQuote 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 acceptNonLpQuote:
{
"version": "1",
"default": "deny",
"tools": {
"acceptNonLpQuote": {
"limits": [
{
"counter": "acceptnonlpquote_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}acceptNonLpQuote stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Enable acceptance of non-LP quotes for a specific RFQ.\nThis allows the inquirer to receive and execute quotes from normal counterparties\nin addition to liquidity providers.\n\nRate Limit: 50 requests per second.\n\nAgent hint: Use this endpoint to allow non-LP counterparties to quote on your RFQ.\nOnly the RFQ creator can call this endpoint. Pass the rfqId of the target RFQ. It is categorised as a Execute tool in the Bybit MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Bybit MCP Server MCP server in PolicyLayer and add a rule for acceptNonLpQuote: 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.
acceptNonLpQuote is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the acceptNonLpQuote 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 acceptNonLpQuote. 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.
acceptNonLpQuote 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.