capability_hash
First principles: content-addressed capability hash (what it does, not who hosts it). Optionally register + bind listing_id.
This record as markdown: /tools/dev-dualregistry-registry/capability-hash.md
What capability_hash does on Dual Registry
AI agents call capability_hash 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 |
|---|---|---|---|
kind | string | — | |
name | string | Yes | |
tags | array | — | |
tools | array | — | |
skills | array | — | |
register | boolean | — | |
listing_id | string | — | |
description | string | — |
Parameters from the server's own tool schema.
Why capability_hash is rated Low
Even though capability_hash 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 capability_hash 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 capability_hash, this is the rule to start with:
capability_hash 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 capability_hash call is checked against it from then on.
Questions about capability_hash
First principles: content-addressed capability hash (what it does, not who hosts it). Optionally register + bind listing_id. It is categorised as a Read tool in the Dual Registry MCP Server, which means it retrieves data without modifying state.
capability_hash accepts 8 parameters: kind, name, tags, tools, skills, register, listing_id, description. Required: name. 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 capability_hash: 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.
capability_hash 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 capability_hash 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 capability_hash. 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.
capability_hash 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