search_circuits
Search 0gzk ZK circuits by natural-language query (matched against names, tags, keywords, use cases, and descriptions). In repo mode this searches the local catalog; without a repo it falls back to substring-matching circuit names on a live registry.
This record as markdown: /tools/0gzk-mcp/search-circuits.md
What search_circuits does on 0gzk
AI agents call search_circuits 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 |
|---|---|---|---|
chain | string | — | Only report publications on this chain (catalog mode) / registry to enumerate (discovery mode) |
limit | integer | — | Maximum results |
query | string | Yes | What the circuit should do, e.g. "prove age over 18" |
Parameters from the server's own tool schema.
Why search_circuits is rated Low
Even though search_circuits 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 search_circuits 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 search_circuits, this is the rule to start with:
search_circuits 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 search_circuits call is checked against it from then on.
Questions about search_circuits
Search 0gzk ZK circuits by natural-language query (matched against names, tags, keywords, use cases, and descriptions). In repo mode this searches the local catalog; without a repo it falls back to substring-matching circuit names on a live registry. It is categorised as a Read tool in the 0gzk MCP Server, which means it retrieves data without modifying state.
search_circuits accepts 3 parameters: chain, limit, query. Required: query. 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 search_circuits: 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.
search_circuits 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 search_circuits 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 search_circuits. 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.
search_circuits 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