polymarket.trading.cancel_order
Cancel an open order on Polymarket
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/polymarket.trading.cancel-order.md
What polymarket.trading.cancel_order does on Apibase
AI agents call polymarket.trading.cancel_order to permanently remove resources in Apibase, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
order_id | string | Yes | Polymarket order ID to cancel (from open_orders response) |
Parameters from the server's own tool schema.
Why polymarket.trading.cancel_order is rated Critical
Cancelling an order is irreversible; the market position opportunity is permanently lost.
From the tool's definition Cancel an open order on Polymarket
Attacks that exploit this kind of access
The rule that runs polymarket.trading.cancel_order safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For polymarket.trading.cancel_order, this is the rule to start with:
polymarket.trading.cancel_order is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every polymarket.trading.cancel_order call is checked against it from then on.
Questions about polymarket.trading.cancel_order
Cancel an open order on Polymarket. It is categorised as a Destructive tool in the Apibase MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
polymarket.trading.cancel_order accepts 1 parameter: order_id. Required: order_id. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for polymarket.trading.cancel_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 Apibase. Nothing to install.
polymarket.trading.cancel_order 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 polymarket.trading.cancel_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 polymarket.trading.cancel_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.
polymarket.trading.cancel_order is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
Across the catalogue