prove_circuit
Generate a Groth16 proof (and locally verify it) for a circuit, optionally saving the artifacts to disk. Bundle source: a repo circuit's circuit_bundle/ by name (falling back to the published registry bundle), an explicit bundleDir, or a published rootHash fetched into the cache. Input validation...
This record as markdown: /tools/0gzk-mcp/prove-circuit.md
What prove_circuit does on 0gzk
AI agents call prove_circuit to retrieve information from 0gzk without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | Circuit name (repo circuit_bundle/ preferred, registry fallback) |
chain | string | — | Registry/storage chain for fetches (default base) |
inputs | object | — | Circuit inputs keyed by signal name (field elements as decimal strings) |
outDir | string | — | Directory for proof.json, public.json and result.json. Defaults to ~/.0gzk/proofs/<circuit>-<timestamp>/. The absolute path is always returned as saved.outDir. |
verify | boolean | — | |
rootHash | string | — | Published bundle rootHash (0x...) |
bundleDir | string | — | Directory containing an extracted bundle |
inputFile | string | — | Path to a JSON file of inputs, read locally — use instead of `inputs` to keep values off the wire |
Parameters from the server's own tool schema.
Why prove_circuit is rated Low
Even though prove_circuit only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs prove_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 prove_circuit, this is the rule to start with:
prove_circuit is read-only, so it stays allowed. 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 prove_circuit call is checked against it from then on.
Questions about prove_circuit
Generate a Groth16 proof (and locally verify it) for a circuit, optionally saving the artifacts to disk. Bundle source: a repo circuit's circuit_bundle/ by name (falling back to the published registry bundle), an explicit bundleDir, or a published rootHash fetched into the cache. Input validation errors describe the exact expected input schema. Proving runs wherever this tool executes — the witness never leaves that machine. It is categorised as a Read tool in the 0gzk MCP Server, which means it retrieves data without modifying state.
prove_circuit accepts 8 parameters: name, chain, inputs, outDir, verify, rootHash, bundleDir, inputFile. 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 prove_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.
prove_circuit is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the prove_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 prove_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.
prove_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