get_circuit
Get the full record for one circuit: metadata (inputs/outputs), constraints, example input, publications, and how to prove with it. Unknown names can be resolved from a live registry and their published bundle fetched into the local cache.
This record as markdown: /tools/0gzk-mcp/get-circuit.md
What get_circuit does on 0gzk
AI agents call get_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 | Yes | |
chain | string | — | Registry chain for non-catalog circuits (default base) |
version | string | — | Registry version (defaults to latest) |
fetchIfMissing | boolean | — | Allow downloading the published bundle when the circuit is not in the catalog |
includeExampleInput | boolean | — |
Parameters from the server's own tool schema.
Why get_circuit is rated Low
Even though get_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 get_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 get_circuit, this is the rule to start with:
get_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 get_circuit call is checked against it from then on.
Questions about get_circuit
Get the full record for one circuit: metadata (inputs/outputs), constraints, example input, publications, and how to prove with it. Unknown names can be resolved from a live registry and their published bundle fetched into the local cache. It is categorised as a Read tool in the 0gzk MCP Server, which means it retrieves data without modifying state.
get_circuit accepts 5 parameters: name, chain, version, fetchIfMissing, includeExampleInput. Required: name. 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 get_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.
get_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 get_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 get_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.
get_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