theprotocol_getAttestationBundle
Get the registry-signed bundle of an attestation (proof_b64, proof_hash, public_inputs, verified, revoked, valid_until, Ed25519 signature) for offline checks: the signature with getAttestationSigningPubkey, the proof with bb verify against the circuit's verification key (/api/v1/circuits/{id}/vk).
This record as markdown: /tools/cloud-theprotocol-registry/theprotocol-getattestationbundle.md
What theprotocol_getAttestationBundle does on TheProtocol — Sovereign AI Agent Platform
AI agents call theprotocol_getAttestationBundle 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
attestation_id | string | Yes |
Parameters from the server's own tool schema.
Why theprotocol_getAttestationBundle is rated Low
Even though theprotocol_getAttestationBundle 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
The rule that runs theprotocol_getAttestationBundle 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_getAttestationBundle, this is the rule to start with:
theprotocol_getAttestationBundle 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_getAttestationBundle call is checked against it from then on.
Questions about theprotocol_getAttestationBundle
Get the registry-signed bundle of an attestation (proof_b64, proof_hash, public_inputs, verified, revoked, valid_until, Ed25519 signature) for offline checks: the signature with getAttestationSigningPubkey, the proof with bb verify against the circuit's verification key (/api/v1/circuits/{id}/vk). It is categorised as a Read tool in the TheProtocol — Sovereign AI Agent Platform MCP Server, which means it retrieves data without modifying state.
theprotocol_getAttestationBundle accepts 1 parameter: attestation_id. Required: attestation_id. 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_getAttestationBundle: 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_getAttestationBundle 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_getAttestationBundle 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_getAttestationBundle. 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_getAttestationBundle 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