bind_identity
First principles: bind cryptographic identity (DID / public key) to listing + content-addressed capability.
This record as markdown: /tools/dev-dualregistry-registry/bind-identity.md
What bind_identity does on Dual Registry
AI agents call bind_identity to retrieve information from Dual Registry 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 | — | |
name | string | — | |
listing_id | string | Yes | |
public_jwk | object | — | |
public_key_pem | string | — |
Parameters from the server's own tool schema.
Why bind_identity is rated Low
Even though bind_identity 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.
Attacks that exploit this kind of access
The rule that runs bind_identity safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dual Registry, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bind_identity, this is the rule to start with:
bind_identity 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 Dual Registry, apply this rule, and every bind_identity call is checked against it from then on.
Questions about bind_identity
First principles: bind cryptographic identity (DID / public key) to listing + content-addressed capability. It is categorised as a Read tool in the Dual Registry MCP Server, which means it retrieves data without modifying state.
bind_identity accepts 5 parameters: did, name, listing_id, public_jwk, public_key_pem. Required: listing_id. The full parameter table on this page comes from the server's own tool schema.
Register the Dual Registry MCP server in PolicyLayer and add a rule for bind_identity: 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 Dual Registry. Nothing to install.
bind_identity 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_identity 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_identity. 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_identity is provided by the Dual Registry MCP server (https://www.dualregistry.dev/api/protocol). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dual Registry, and thousands of servers like it.
This server
Across the catalogue