# orderbook

[Requires authentication] This tool needs OAuth. If it returns an authentication error, prompt the user to connect/authenticate this MCP server (OAuth), then retry. Limit orders via the 1inch Orderbook API (v4.1). IMPORTANT: The "action" parameter is REQUIRED. Must be one of: "build", "create", "list", "cancel". Actions with example parameters: 1. build (recommended first step): { "action": "build", "chain": 1, "makerAsset": "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48", "takerAsset": "0xdAC17F958D2ee523a2206206994597C13D831ec7", "makingAmount": "1000000", "takingAmount": "990000", "makerAddress": "0x..." } Optional: expirationSeconds (default 604800 = 7 days). With an active WalletConnect session, the order is signed and submitted automatically (set execute=false to return typed data only). 2. create (after signing typedData from build): { "action": "create", "chain": 1, "orderHash": "0x...", "signature": "0x...", "orderData": { ... } } 3. list (query orders): - By maker: { "action": "list", "chain": 1, "listMode": "by_maker", "makerAddress": "0x..." } - By hash: { "action": "list", "chain": 1, "listMode": "by_hash", "orderHash": "0x..." } - Browse: { "action": "list", "chain": 1, "listMode": "all", "limit": 10 } 4. cancel (inspect + guidance): { "action": "cancel", "chain": 1, "orderHash": "0x..." } Typical flow: build -> sign typedData -> create (or one build call when WalletConnect is connected — order signed and submitted automatically). The maker asset may require a one-time ERC-20 approval for the Limit Order Protocol; it costs native gas even though the limit order itself is gasless. When a build response includes an "approval" block, tell the user upfront (approval.estimatedCost holds the estimated cost in native units) and broadcast the included approveTx before signing. With WalletConnect, the approve is sent automatically — "approvalTxSent": true means the first wallet prompt was the one-time approval. Requires authentication. For raw HTTP access, use product_api.

Agent View of the PolicyLayer registry record for `orderbook`. HTML page: https://policylayer.com/tools/com-1inch-business-mcp/orderbook

## Facts

- Tool: `orderbook`
- Server: 1inch MCP (`https://api.1inch.com/mcp/protocol`) — https://policylayer.com/tools/com-1inch-business-mcp.md
- Homepage: https://github.com/1inch/1inch-ai
- Risk category: Financial (Critical risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Approval-gated

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

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

## Why orderbook is rated Critical

This tool creates and manages limit orders on a DEX (1inch), which are financial commitments to swap tokens at specified prices. Creating an order commits the maker's assets to a trade. This is a financial operation with high blast radius if misused — an AI agent could create orders that transfer valuable tokens at unfavorable rates or without user intent.

From the tool's own definition: "Limit orders via the 1inch Orderbook API (v4.1). Actions include: build, create, list, cancel — creating and managing on-chain limit orders involving token swaps."

## Use case

AI agents use orderbook to commit financial operations through 1inch MCP, usually the final step of a payment, billing, or trading workflow. A call moves real money.

## Recommended policy (PolicyLayer)

Verdict: **Approval-gated**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches 1inch MCP:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "orderbook": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}
```

## Other tools on 1inch MCP (8)

- `product_api` — Financial — https://policylayer.com/tools/com-1inch-business-mcp/product-api.md
- `swap` — Financial — https://policylayer.com/tools/com-1inch-business-mcp/swap.md
- `walletconnect` — Financial — https://policylayer.com/tools/com-1inch-business-mcp/walletconnect.md
- `aqua` — Read — https://policylayer.com/tools/com-1inch-business-mcp/aqua.md
- `debug` — Read — https://policylayer.com/tools/com-1inch-business-mcp/debug.md
- `get_example` — Read — https://policylayer.com/tools/com-1inch-business-mcp/get-example.md
- `list_examples` — Read — https://policylayer.com/tools/com-1inch-business-mcp/list-examples.md
- `search` — Read — https://policylayer.com/tools/com-1inch-business-mcp/search.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=com-1inch-business-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-1inch-business-mcp