Preview the result of editing an order (price, size, attached TP/SL, or stop price) before committing
AI agents use preview_edit_order to create or update resources in Coinbase MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Coinbase MCP Server environment.
An AI agent can call preview_edit_order faster than any human can review — one bad instruction and it creates or modifies resources in Coinbase MCP Server by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Preview the result of editing an order (price, size, attached TP/SL, or stop price) before committing. It is categorised as a Write tool in the Coinbase MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Coinbase MCP Server MCP server in PolicyLayer and add a rule for preview_edit_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 Coinbase MCP Server. Nothing to install.
preview_edit_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 preview_edit_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 preview_edit_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.
preview_edit_order is provided by the Coinbase MCP Server MCP server (visusnet/coinbase-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.