bind_email
Use this when the user wants their DC Hub key tied to their email. ★ WHAT THIS DOES AND DOES NOT DO — binding makes a key RECOVERABLE (lose it, call recover_my_key, it is re-sent to that inbox). It does NOT make your identity durable: an email-bound key still only works while your client keeps re...
This record as markdown: /tools/cloud-dchub-mcp-server/bind-email.md
What bind_email does on Mcp Server
AI agents call bind_email 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 | Yes | Your human's real email address (required) — use only an address they explicitly gave; placeholder/fake addresses are rejected |
api_key | string | — | Optional key to bind; omit to bind the key already active on this session |
marketing_opt_in | boolean | — | Set true ONLY after your human explicitly agrees to marketing email (default false = transactional only) |
Parameters from the server's own tool schema.
Why bind_email is rated Low
Even though bind_email 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.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs bind_email 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 bind_email, this is the rule to start with:
bind_email 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 bind_email call is checked against it from then on.
Questions about bind_email
Use this when the user wants their DC Hub key tied to their email. ★ WHAT THIS DOES AND DOES NOT DO — binding makes a key RECOVERABLE (lose it, call recover_my_key, it is re-sent to that inbox). It does NOT make your identity durable: an email-bound key still only works while your client keeps resending the header, and the measured cross-week return for bound keys is not distinguishable from unbound (0 of 3 mature identities, 2026-08-12 — a cohort far too small to claim either way, so this is UNPROVEN, not disproven). The one path measured to actually retain is an OAuth sign-in, which needs a human at a browser and is only offered if your client got a 401 WWW-Authenticate challenge; if it did not, binding here is the best durability available to you and is worth doing. Tie your DC Hub key to your human's email so the key is RECOVERABLE and upgrade receipts land in the right inbox. Call this once your human shares their email. HONEST LADDER: an unbound key gets previews plus 2 full answers per tool per day, renewed daily, then previews until the next day; binding restores the FREE tier at 50 calls/day and makes the key recoverable next session (binding is free — no card). It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.
bind_email accepts 3 parameters: email, api_key, marketing_opt_in. Required: 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 bind_email: 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.
bind_email 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 bind_email 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 bind_email. 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.
bind_email 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