This record as markdown: /tools/johnnywic-bybit-mcp/amend-spread-order.md
What amend_spread_order does on Bybit
AI agents use amend_spread_order 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 amend_spread_order is rated Medium
Amending a spread trading order modifies an existing financial order on Bybit exchange. While it modifies trading state (Write), it doesn't directly move money or commit new financial obligations — it changes parameters of an existing order. However, amending orders on a live exchange has high blast radius as it can significantly affect trading positions and financial outcomes.
From the tool's definition Amend a spread trading order
Attacks that exploit this kind of access
The rule that runs amend_spread_order 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 amend_spread_order, this is the rule to start with:
amend_spread_order 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 amend_spread_order call is checked against it from then on.
Questions about amend_spread_order
Amend a spread trading order. 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 amend_spread_order: 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.
amend_spread_order 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 amend_spread_order 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 amend_spread_order. 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.
amend_spread_order 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