match_capability
Capability matchmaking — rank Active clean listings for a natural-language need. Ranking includes stigmergic usage pheromones (trail-following).
This record as markdown: /tools/dev-dualregistry-registry/match-capability.md
What match_capability does on Dual Registry
AI agents call match_capability 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 |
|---|---|---|---|
q | string | Yes | What capability you need, e.g. 'github issues MCP' |
kind | string | — | |
limit | number | — | |
federation | string | — |
Parameters from the server's own tool schema.
Why match_capability is rated Low
Even though match_capability 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 match_capability 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 match_capability, this is the rule to start with:
match_capability 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 match_capability call is checked against it from then on.
Questions about match_capability
Capability matchmaking — rank Active clean listings for a natural-language need. Ranking includes stigmergic usage pheromones (trail-following). It is categorised as a Read tool in the Dual Registry MCP Server, which means it retrieves data without modifying state.
match_capability accepts 4 parameters: q, kind, limit, federation. Required: q. 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 match_capability: 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.
match_capability 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 match_capability 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 match_capability. 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.
match_capability 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