verify_zk_proof
Verify a Plonky3 STARK proof over the KoalaBear field.
This record as markdown: /tools/network-tenzro-tenzro/verify-zk-proof.md
What verify_zk_proof does on Tenzro Ledger MCP
AI agents call verify_zk_proof to retrieve information from Tenzro Ledger MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why verify_zk_proof is rated Low
Verification of a zero-knowledge proof is a read/query operation — it checks the validity of a proof without modifying state, moving funds, or executing commands. The result is a boolean validity judgment with no side effects.
From the tool's definition Verify a Plonky3 STARK proof over the KoalaBear field
Attacks that exploit this kind of access
The rule that runs verify_zk_proof safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tenzro Ledger MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For verify_zk_proof, this is the rule to start with:
verify_zk_proof 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 Tenzro Ledger MCP, apply this rule, and every verify_zk_proof call is checked against it from then on.
Questions about verify_zk_proof
Verify a Plonky3 STARK proof over the KoalaBear field. 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 verify_zk_proof: 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.
verify_zk_proof 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 verify_zk_proof 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 verify_zk_proof. 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.
verify_zk_proof 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.
More on Tenzro Ledger, and thousands of servers like it.
This server
Across the catalogue