Cancel all open orders in a specific market.
AI agents call cancel_market_orders to permanently remove resources in Polymarket MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cancelling all open orders in a market is an irreversible action — once orders are cancelled, any queue position, pricing, or market opportunity is lost and cannot be restored. This is a bulk destructive operation affecting all open orders in a given market, with high blast radius if misused by an AI agent (e.g., cancelling all orders unintentionally during active trading).
From the tool's definition Cancel all open orders in a specific market
Attacks that exploit this kind of access
Cancel all open orders in a specific market. It is categorised as a Destructive tool in the Polymarket MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Polymarket MCP Server MCP server in PolicyLayer and add a rule for cancel_market_orders: 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 Polymarket MCP Server. Nothing to install.
cancel_market_orders is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the cancel_market_orders 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 cancel_market_orders. 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.
cancel_market_orders is provided by the Polymarket MCP Server MCP server (nancheng582-jpg/polymarket-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 →