search_docs

Search the devrel.directory unified index of documentation guides, blog posts, directory listings, jobs, and events (including which have an open call for papers). Returns matching results with absolute devrel.directory URLs; event results deep-link to the specific event on the events page.

SERVERDevRel Directory SOURCEhttps://devrel.directory/mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/directory-devrel-devrel-directory/search-docs.md

WHAT IT DOES

What search_docs does on DevRel Directory

AI agents call search_docs 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	Yes	The search query.

Parameters from the server's own tool schema.

RISK

Why search_docs is rated Low

Even though search_docs 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 search_docs 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_docs, this is the rule to start with:

search_docs Allowed

search_docs 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": {
    "search_docs": {}
  }
}

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

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

FAQ

Questions about search_docs

What does the search_docs tool do? +

What parameters does search_docs accept? +

search_docs accepts 1 parameter: query. Required: query. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on search_docs? +

Register the DevRel Directory MCP server in PolicyLayer and add a rule for search_docs: 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.

What risk level is search_docs? +

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

Can I rate-limit search_docs? +

Yes. Add a rate_limit block to the search_docs 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 search_docs completely? +

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

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

KEEP EXPLORING

More on DevRel Directory, and thousands of servers like it.

This server

All 6 DevRel Directory tools →

Across the catalogue

evaluate_search_quality on ACE-MCP →search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server → The MCP Attack Database →

Guides

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