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).
This record as markdown: /tools/0gzk-mcp/resolve-circuit.md
What resolve_circuit does on 0gzk
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
spec | string | Yes | Circuit spec, e.g. "age_verification" or "age_verification@0.1.0" |
chain | string | — |
Parameters from the server's own tool schema.
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.
Attacks that exploit this kind of access
The rule that runs resolve_circuit safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 0gzk, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For resolve_circuit, this is the rule to start with:
resolve_circuit stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 0gzk, apply this rule, and every resolve_circuit call is checked against it from then on.
Questions about 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). It is categorised as a Write tool in the 0gzk MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
resolve_circuit accepts 2 parameters: spec, chain. Required: spec. The full parameter table on this page comes from the server's own tool schema.
Register the 0gzk MCP server in PolicyLayer and add a rule for resolve_circuit: 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 0gzk. Nothing to install.
resolve_circuit is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the resolve_circuit 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 resolve_circuit. 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.
resolve_circuit is provided by the 0gzk MCP server (@0gzk/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 0gzk, and thousands of servers like it.
This server
Across the catalogue