theprotocol_getAgentByDID
Get agent profile by DID (public view, no PII). Public — no auth.
This record as markdown: /tools/cloud-theprotocol-registry/theprotocol-getagentbydid.md
What theprotocol_getAgentByDID does on TheProtocol — Sovereign AI Agent Platform
AI agents call theprotocol_getAgentByDID 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 |
|---|---|---|---|
did | string | Yes |
Parameters from the server's own tool schema.
Why theprotocol_getAgentByDID is rated Low
This tool retrieves and queries agent profile data without side effects. The explicit notes that it returns a public view with no PII and requires no authentication confirm it is a passive information retrieval operation. No data is created, modified, deleted, or executed. Blast radius is minimal—the information is already public and no sensitive data is exposed.
From the tool's definition Tool name includes 'Get' and description states 'Get agent profile by DID (public view, no PII). Public — no auth.' This is a read-only retrieval operation returning public data without sensitive information.
Attacks that exploit this kind of access
The rule that runs theprotocol_getAgentByDID 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_getAgentByDID, this is the rule to start with:
theprotocol_getAgentByDID 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_getAgentByDID call is checked against it from then on.
Questions about theprotocol_getAgentByDID
Get agent profile by DID (public view, no PII). 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.
theprotocol_getAgentByDID accepts 1 parameter: did. Required: did. 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_getAgentByDID: 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_getAgentByDID 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_getAgentByDID 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_getAgentByDID. 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_getAgentByDID 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