# resolve_circuit

Resolve a "name" or "name@version" spec against the on-chain registries and report the published record per chain (rootHash, vkeyHash, verifier, publisher, publishedAt).

Agent View of the PolicyLayer registry record for `resolve_circuit`. HTML page: https://policylayer.com/tools/0gzk-mcp/resolve-circuit

## Facts

- Tool: `resolve_circuit`
- Server: 0gzk (`@0gzk/mcp`) — https://policylayer.com/tools/0gzk-mcp.md
- Install: `npx -y @0gzk/mcp`
- Homepage: https://www.npmjs.com/package/@0gzk/mcp
- Risk category: Write (Medium risk)
- Registry record: grade B, identity unverified
- Server rate-limited: no
- Parameters: 2 (1 required)
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `spec` | string | yes | Circuit spec, e.g. "age_verification" or "age_verification@0.1.0" |
| `chain` | string | no |  |

Parameters from the server's own tool schema.

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

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "resolve_circuit",
    "arguments": {
      "spec": "<spec>"
    }
  }
}
```

## Why resolve_circuit is rated Medium

An AI agent can call resolve_circuit faster than any human can review: one bad instruction and it creates or modifies resources in 0gzk by the hundred, each call as confident as the last.

## Use case

AI agents use resolve_circuit to create or update resources in 0gzk, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 0gzk environment.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "resolve_circuit": {
      "limits": [
        {
          "counter": "resolve_circuit_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on 0gzk (7)

- `get_circuit` — Read — https://policylayer.com/tools/0gzk-mcp/get-circuit.md
- `get_example_input` — Read — https://policylayer.com/tools/0gzk-mcp/get-example-input.md
- `list_circuits` — Read — https://policylayer.com/tools/0gzk-mcp/list-circuits.md
- `prove_circuit` — Read — https://policylayer.com/tools/0gzk-mcp/prove-circuit.md
- `read_input_file` — Read — https://policylayer.com/tools/0gzk-mcp/read-input-file.md
- `search_circuits` — Read — https://policylayer.com/tools/0gzk-mcp/search-circuits.md
- `validate_inputs` — Read — https://policylayer.com/tools/0gzk-mcp/validate-inputs.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=0gzk-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0gzk-mcp