Replace an existing order (cancel old and place new) in one atomic operation. Requires authentication.
AI agents invoke replace_order to trigger actions in Derive MCP. 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 atomically cancels an existing order and places a new one in a financial trading context. While it involves financial instruments (options, perpetuals, spot markets), the primary action is order replacement/modification rather than directly moving money. However, it does trigger external trading operations with significant financial impact.
From the tool's definition Replace an existing order (cancel old and place new) in one atomic operation. Requires authentication.
Attacks that exploit this kind of access
Replace an existing order (cancel old and place new) in one atomic operation. Requires authentication. It is categorised as a Execute tool in the Derive MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Derive MCP server in PolicyLayer and add a rule for replace_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 Derive MCP. Nothing to install.
replace_order 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 replace_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 replace_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.
replace_order is provided by the Derive MCP server (solenyaresearch0000/derive-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →