ard_search

Agentic Resource Discovery over Dual catalog + Active projections. POST https://www.dualregistry.dev/api/ard/search

SERVERDual Registry SOURCEhttps://www.dualregistry.dev/api/protocol

Low RISK CLASS

Category Read

Parameters 31 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-dualregistry-registry/ard-search.md

WHAT IT DOES

What ard_search does on Dual Registry

AI agents call ard_search 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
`q`	string	Yes
`limit`	number	—
`federation`	string	—

Parameters from the server's own tool schema.

RISK

Why ard_search is rated Low

Even though ard_search 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

RECOMMENDED RULE

The rule that runs ard_search 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 ard_search, this is the rule to start with:

ard_search Allowed

ard_search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ard_search": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Dual Registry, apply this rule, and every ard_search call is checked against it from then on.

FAQ

Questions about ard_search

What does the ard_search tool do? +

Agentic Resource Discovery over Dual catalog + Active projections. POST https://www.dualregistry.dev/api/ard/search. It is categorised as a Read tool in the Dual Registry MCP Server, which means it retrieves data without modifying state.

What parameters does ard_search accept? +

ard_search accepts 3 parameters: q, limit, federation. Required: q. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on ard_search? +

Register the Dual Registry MCP server in PolicyLayer and add a rule for ard_search: 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.

What risk level is ard_search? +

ard_search is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit ard_search? +

Yes. Add a rate_limit block to the ard_search 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.

How do I block ard_search completely? +

Set action: deny in the PolicyLayer policy for ard_search. 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.

What MCP server provides ard_search? +

ard_search 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.

KEEP EXPLORING

More on Dual Registry, and thousands of servers like it.

This server

All 64 Dual Registry tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →hybrid_search on Azure AI Agent Service + Azure AI Search MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →