theprotocol_getCircuits
Catalog of ZKP circuits available on this registry (circuit_id, name, ACIR/source URLs). Public — no auth.
This record as markdown: /tools/cloud-theprotocol-registry/theprotocol-getcircuits.md
What theprotocol_getCircuits does on TheProtocol — Sovereign AI Agent Platform
AI agents call theprotocol_getCircuits to retrieve information from TheProtocol — Sovereign AI Agent Platform without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why theprotocol_getCircuits is rated Low
This tool queries and returns information about zero-knowledge proof circuits without side effects. It performs a read operation (list/discovery) of public registry data. No data modification, deletion, code execution, or financial transaction occurs. The public nature and explicit lack of authentication further confirm this is safe read-only access.
From the tool's definition Tool description states it retrieves a 'Catalog of ZKP circuits' with metadata (circuit_id, name, URLs). The verb 'Catalog' and listed fields indicate data retrieval. Explicitly marked 'Public — no auth', indicating read-only discovery access.
Attacks that exploit this kind of access
The rule that runs theprotocol_getCircuits safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TheProtocol — Sovereign AI Agent Platform, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For theprotocol_getCircuits, this is the rule to start with:
theprotocol_getCircuits 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 TheProtocol — Sovereign AI Agent Platform, apply this rule, and every theprotocol_getCircuits call is checked against it from then on.
Questions about theprotocol_getCircuits
Catalog of ZKP circuits available on this registry (circuit_id, name, ACIR/source URLs). Public — no auth. It is categorised as a Read tool in the TheProtocol — Sovereign AI Agent Platform MCP Server, which means it retrieves data without modifying state.
Register the TheProtocol — Sovereign AI Agent Platform MCP server in PolicyLayer and add a rule for theprotocol_getCircuits: 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 TheProtocol — Sovereign AI Agent Platform. Nothing to install.
theprotocol_getCircuits 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 theprotocol_getCircuits 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 theprotocol_getCircuits. 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.
theprotocol_getCircuits is provided by the TheProtocol — Sovereign AI Agent Platform MCP server (https://api.theprotocol.cloud/mcp/sse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on TheProtocol — Sovereign AI Agent Platform, and thousands of servers like it.
Across the catalogue