# polymarket_cancel_order

Cancel an existing order. Requires API key authentication.

Agent View of the PolicyLayer registry record for `polymarket_cancel_order`. HTML page: https://policylayer.com/tools/asthetech-cl-mcp-polymarket/polymarket-cancel-order

## Facts

- Tool: `polymarket_cancel_order`
- Server: Polymarket MCP Server (`asthetech/mewcp-polymarket`) — https://policylayer.com/tools/asthetech-cl-mcp-polymarket.md
- Homepage: https://github.com/AStheTECH/mewcp-polymarket
- Risk category: Destructive (Critical risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Hidden

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "polymarket_cancel_order",
    "arguments": {}
  }
}
```

## Why polymarket_cancel_order is rated Critical

An AI agent that decides to call polymarket_cancel_order doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Polymarket MCP Server is gone. There is no undo for destructive operations.

## Use case

AI agents call polymarket_cancel_order 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.

## Recommended policy (PolicyLayer)

Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Polymarket MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "polymarket_cancel_order"
  ]
}
```

## Other tools on Polymarket MCP Server (10)

- `polymarket_create_order` — Financial — https://policylayer.com/tools/asthetech-cl-mcp-polymarket/polymarket-create-order.md
- `polymarket_get_events` — Read — https://policylayer.com/tools/asthetech-cl-mcp-polymarket/polymarket-get-events.md
- `polymarket_get_market` — Read — https://policylayer.com/tools/asthetech-cl-mcp-polymarket/polymarket-get-market.md
- `polymarket_get_markets` — Read — https://policylayer.com/tools/asthetech-cl-mcp-polymarket/polymarket-get-markets.md
- `polymarket_get_midpoint` — Read — https://policylayer.com/tools/asthetech-cl-mcp-polymarket/polymarket-get-midpoint.md
- `polymarket_get_orderbook` — Read — https://policylayer.com/tools/asthetech-cl-mcp-polymarket/polymarket-get-orderbook.md
- `polymarket_get_orders` — Read — https://policylayer.com/tools/asthetech-cl-mcp-polymarket/polymarket-get-orders.md
- `polymarket_get_user_positions` — Read — https://policylayer.com/tools/asthetech-cl-mcp-polymarket/polymarket-get-user-positions.md
- `polymarket_get_user_trades` — Read — https://policylayer.com/tools/asthetech-cl-mcp-polymarket/polymarket-get-user-trades.md
- `polymarket_health_check` — Read — https://policylayer.com/tools/asthetech-cl-mcp-polymarket/polymarket-health-check.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=asthetech-cl-mcp-polymarket · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/asthetech-cl-mcp-polymarket