theprotocol_getRevokedIdentities
Revoked IRONHAND mTLS identities (cross-frame revocation). Agent JWT.
This record as markdown: /tools/cloud-theprotocol-registry/theprotocol-getrevokedidentities.md
What theprotocol_getRevokedIdentities does on TheProtocol — Sovereign AI Agent Platform
AI agents call theprotocol_getRevokedIdentities 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 |
|---|---|---|---|
agent_jwt | string | — |
Parameters from the server's own tool schema.
Why theprotocol_getRevokedIdentities is rated Low
This tool retrieves or queries a list of revoked identities for authentication/authorization purposes. No data is created, modified, deleted, or executed. The operation is informational only, used to check revocation status. Severity is low because misuse would only expose or return existing revocation data without enabling attacks on the identity system itself—actual enforcement of revocations happens elsewhere.
From the tool's definition Tool name 'getRevokedIdentities' and description explicitly states it retrieves 'Revoked IRONHAND mTLS identities' — a read-only query operation with no side effects.
Attacks that exploit this kind of access
The rule that runs theprotocol_getRevokedIdentities 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_getRevokedIdentities, this is the rule to start with:
theprotocol_getRevokedIdentities 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_getRevokedIdentities call is checked against it from then on.
Questions about theprotocol_getRevokedIdentities
Revoked IRONHAND mTLS identities (cross-frame revocation). Agent JWT. 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_getRevokedIdentities accepts 1 parameter: agent_jwt. 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_getRevokedIdentities: 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_getRevokedIdentities 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_getRevokedIdentities 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_getRevokedIdentities. 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_getRevokedIdentities 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