recover_my_key
Recover a LOST DC Hub key. Pass your human's email and DC Hub re-sends any key tied to that address to that inbox. It NEVER returns the key over the wire (it emails the bound address), and the confirmation is the same whether or not a key exists (enumeration-safe), so no key is leaked to a caller...
This record as markdown: /tools/cloud-dchub-mcp-server/recover-my-key.md
What recover_my_key does on Mcp Server
AI agents call recover_my_key to retrieve information from Mcp Server 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 |
|---|---|---|---|
email | string | — | Your human's email address that a lost key was bound to (required) — the key is re-sent to that inbox, never returned over the wire |
Parameters from the server's own tool schema.
Why recover_my_key is rated Low
This tool retrieves/recovers account access credentials by triggering a password/key recovery flow to a registered email address. It is purely informational from the caller's perspective—it performs a lookup and notification action but does not modify, execute code, destroy data, or move funds.
From the tool's definition 'Recover a LOST DC Hub key' via email recovery mechanism; 'NEVER returns the key over the wire'; 're-sends any key tied to that address to that inbox'; 'confirmation is the same whether or not a key exists (enumeration-safe)'
Attacks that exploit this kind of access
The rule that runs recover_my_key safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For recover_my_key, this is the rule to start with:
recover_my_key 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 Mcp Server, apply this rule, and every recover_my_key call is checked against it from then on.
Questions about recover_my_key
Recover a LOST DC Hub key. Pass your human's email and DC Hub re-sends any key tied to that address to that inbox. It NEVER returns the key over the wire (it emails the bound address), and the confirmation is the same whether or not a key exists (enumeration-safe), so no key is leaked to a caller. Use this when your human had a key, lost it, and knows the email they bound it to. Param: email (required). Returns DC Hub's neutral confirmation. It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.
recover_my_key accepts 1 parameter: email. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Server MCP server in PolicyLayer and add a rule for recover_my_key: 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 Mcp Server. Nothing to install.
recover_my_key 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 recover_my_key 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 recover_my_key. 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.
recover_my_key is provided by the Mcp Server MCP server (https://dchub.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Server, and thousands of servers like it.
This server
Across the catalogue