# authenticate

Call this to start or confirm 1inch Business login. HTTP 401 means you are still anonymous (initialize 200 is not login). After OAuth, call again until the result is authenticated: true with organizationId. Then use swap, orderbook, product_api, or debug. Do not treat a PaymentRequired / x402 result as login.

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

## Facts

- Tool: `authenticate`
- 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: Execute (High risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

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

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

## Why authenticate is rated High

Initiates authentication workflow that enables access to financial operations like swaps and orderbook.

From the tool's own definition: "start or confirm 1inch Business login, OAuth, authenticated"

## Use case

AI agents invoke authenticate to trigger actions in 1inch MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "authenticate": {
      "limits": [
        {
          "counter": "authenticate_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on 1inch MCP (9)

- `product_api` — Destructive — https://policylayer.com/tools/com-1inch-business-mcp/product-api.md
- `walletconnect` — Destructive — https://policylayer.com/tools/com-1inch-business-mcp/walletconnect.md
- `aqua` — Execute — https://policylayer.com/tools/com-1inch-business-mcp/aqua.md
- `orderbook` — Financial — https://policylayer.com/tools/com-1inch-business-mcp/orderbook.md
- `swap` — Financial — https://policylayer.com/tools/com-1inch-business-mcp/swap.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
