theprotocol_getMySigningKeys
List your developer Ed25519 signing keys.
This record as markdown: /tools/cloud-theprotocol-registry/theprotocol-getmysigningkeys.md
What theprotocol_getMySigningKeys does on TheProtocol — Sovereign AI Agent Platform
AI agents call theprotocol_getMySigningKeys 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_getMySigningKeys is rated Low
This tool retrieves/queries existing signing keys owned by the developer with no side effects. It is a straightforward read operation. While signing keys are sensitive credentials, listing them is not itself a destructive or financial action — the risk lies in what an attacker could do with the keys afterward, not in the tool's function.
From the tool's definition Tool name and description: 'List your developer Ed25519 signing keys' — performs a retrieval operation with the verb 'List' and no modification or destruction of data.
Attacks that exploit this kind of access
The rule that runs theprotocol_getMySigningKeys 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_getMySigningKeys, this is the rule to start with:
theprotocol_getMySigningKeys 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_getMySigningKeys call is checked against it from then on.
Questions about theprotocol_getMySigningKeys
List your developer Ed25519 signing keys. 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_getMySigningKeys: 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_getMySigningKeys 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_getMySigningKeys 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_getMySigningKeys. 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_getMySigningKeys 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