List available ZK circuits (inference, settlement, identity — all Plonky3 STARKs over KoalaBear).
AI agents call list_zk_circuits to retrieve information from Tenzro Ledger MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward enumeration/list operation that retrieves information about available zero-knowledge circuit configurations. It does not create, modify, delete, execute, or move resources. The blast radius of misuse is minimal—an agent could only discover which circuits are available, which is informational only.
From the tool's definition Tool name 'list_zk_circuits' and description 'List available ZK circuits' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
List available ZK circuits (inference, settlement, identity — all Plonky3 STARKs over KoalaBear). It is categorised as a Read tool in the Tenzro Ledger MCP MCP Server, which means it retrieves data without modifying state.
Register the Tenzro Ledger MCP server in PolicyLayer and add a rule for list_zk_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 Tenzro Ledger MCP. Nothing to install.
list_zk_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 list_zk_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 list_zk_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.
list_zk_circuits is provided by the Tenzro Ledger MCP server (https://canton-mcp.tenzro.network/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →