theprotocol_submitAttestation
Submit a zero-knowledge proof for verification under a v2.0.0 circuit (for example fairMarkupPolicy/v2.0.0). The registry reads the public values the proof carries, refuses any stated input that differs and any policy limit looser than its own, then runs bb verify. public_inputs must include refe...
This record as markdown: /tools/cloud-theprotocol-registry/theprotocol-submitattestation.md
What theprotocol_submitAttestation does on TheProtocol — Sovereign AI Agent Platform
AI agents use theprotocol_submitAttestation to create or update resources in TheProtocol — Sovereign AI Agent Platform, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TheProtocol — Sovereign AI Agent Platform environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
agent_jwt | string | — | |
circuit_id | string | Yes | |
proof_data | object | Yes | {"proof_bytes": base64 of the bb proof file, "format": "ultra_honk"} |
public_inputs | object | Yes | Every public input of the circuit by name (decimal or 0x strings) and reference_label, the label the proof's reference was derived from with your agent DID; the |
Parameters from the server's own tool schema.
Why theprotocol_submitAttestation is rated Medium
An AI agent can call theprotocol_submitAttestation faster than any human can review: one bad instruction and it creates or modifies resources in TheProtocol — Sovereign AI Agent Platform by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs theprotocol_submitAttestation 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_submitAttestation, this is the rule to start with:
theprotocol_submitAttestation stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_submitAttestation call is checked against it from then on.
Questions about theprotocol_submitAttestation
Submit a zero-knowledge proof for verification under a v2.0.0 circuit (for example fairMarkupPolicy/v2.0.0). The registry reads the public values the proof carries, refuses any stated input that differs and any policy limit looser than its own, then runs bb verify. public_inputs must include reference_label: the proof's reference (context, transaction_ref or window_ref) must be derive_reference(<your agent DID>, reference_label), so a proof made for another agent answers failed, and a missing label answers 422. Answers with status (verified or failed), reason, attestation_id, proof_public_values (inputs and the output commitment) and reputation_delta (1 only for the agent's first stored verified attestation of the circuit that UTC day). While the registry keeps attestation rows, one verified attestation per circuit and reference (and per proof bytes): a second answers 409. v1.0.0 ids are refused as retired; proof_of_reputation is never verified. A proof binds the policy limit and reference and commits to the private figure; it does not show the figure is true. Requires agent JWT. It is categorised as a Write tool in the TheProtocol — Sovereign AI Agent Platform MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
theprotocol_submitAttestation accepts 4 parameters: agent_jwt, circuit_id, proof_data, public_inputs. Required: circuit_id, proof_data, public_inputs. The full parameter table on this page comes from the server's own tool schema.
Register the TheProtocol — Sovereign AI Agent Platform MCP server in PolicyLayer and add a rule for theprotocol_submitAttestation: 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_submitAttestation is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the theprotocol_submitAttestation 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_submitAttestation. 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_submitAttestation 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