list_circuits

List known circuits. source=catalog lists the local repo catalog (name/version/description/tags/publications); source=registry pages through the live on-chain registry for a chain.

SERVER0gzk SOURCE@0gzk/mcp

Low RISK CLASS

Category Read

Parameters 40 required

Recommended Allowedsee the rule below

Registry record Grade B, identity unverified Pull the record →

This record as markdown: /tools/0gzk-mcp/list-circuits.md

WHAT IT DOES

What list_circuits does on 0gzk

AI agents call list_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	—	Registry chain (source=registry)
`limit`	integer	—
`offset`	integer	—
`source`	string	—	Defaults to catalog; falls back to registry when no catalog is available

Parameters from the server's own tool schema.

RISK

Why list_circuits is rated Low

Even though list_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

RECOMMENDED RULE

The rule that runs list_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 list_circuits, this is the rule to start with:

list_circuits Allowed

list_circuits is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_circuits": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect 0gzk, apply this rule, and every list_circuits call is checked against it from then on.

FAQ

Questions about list_circuits

What does the list_circuits tool do? +

List known circuits. source=catalog lists the local repo catalog (name/version/description/tags/publications); source=registry pages through the live on-chain registry for a chain. It is categorised as a Read tool in the 0gzk MCP Server, which means it retrieves data without modifying state.

What parameters does list_circuits accept? +

list_circuits accepts 4 parameters: chain, limit, offset, source. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on list_circuits? +

Register the 0gzk MCP server in PolicyLayer and add a rule for list_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.

What risk level is list_circuits? +

list_circuits is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_circuits? +

Yes. Add a rate_limit block to the list_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.

How do I block list_circuits completely? +

Set action: deny in the PolicyLayer policy for list_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.

What MCP server provides list_circuits? +

list_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.

KEEP EXPLORING

More on 0gzk, and thousands of servers like it.

This server

All 8 0gzk tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →