search_directory
Search the devrel.directory listings of DevRel tools, communities, newsletters, podcasts, and agencies. Filter by a free-text query (matched against name, description, and tags) and/or an exact category. Each result includes the external url and a canonicalUrl to the listing's page on devrel.dire...
This record as markdown: /tools/directory-devrel-devrel-directory/search-directory.md
What search_directory does on DevRel Directory
AI agents call search_directory to retrieve information from DevRel Directory 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 |
|---|---|---|---|
query | string | — | Case-insensitive substring matched against name, description, and tags. |
category | string | — | Exact listing category to filter to. |
Parameters from the server's own tool schema.
Why search_directory is rated Low
Even though search_directory 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 search_directory safely
PolicyLayer is an MCP gateway: it sits between your AI agents and DevRel Directory, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_directory, this is the rule to start with:
search_directory 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 DevRel Directory, apply this rule, and every search_directory call is checked against it from then on.
Questions about search_directory
Search the devrel.directory listings of DevRel tools, communities, newsletters, podcasts, and agencies. Filter by a free-text query (matched against name, description, and tags) and/or an exact category. Each result includes the external url and a canonicalUrl to the listing's page on devrel.directory. It is categorised as a Read tool in the DevRel Directory MCP Server, which means it retrieves data without modifying state.
search_directory accepts 2 parameters: query, category. The full parameter table on this page comes from the server's own tool schema.
Register the DevRel Directory MCP server in PolicyLayer and add a rule for search_directory: 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 DevRel Directory. Nothing to install.
search_directory 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 search_directory 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 search_directory. 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.
search_directory is provided by the DevRel Directory MCP server (https://devrel.directory/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on DevRel Directory, and thousands of servers like it.
This server
Across the catalogue