Search through DevDocs documentation
AI agents call search_devdocs to retrieve information from MCP Developer Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a search operation on documentation sources, which is a non-destructive read operation. It retrieves and queries data without creating, modifying, deleting, or executing any code. The blast radius of misuse is minimal—at worst, an AI agent could retrieve irrelevant or excessive documentation, but no actual systems or data would be compromised.
From the tool's definition Tool name 'search_devdocs' and description 'Search through DevDocs documentation' indicate a query operation that retrieves information without modification or side effects.
Attacks that exploit this kind of access
Search through DevDocs documentation. It is categorised as a Read tool in the MCP Developer Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Developer Server MCP server in PolicyLayer and add a rule for search_devdocs: 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 MCP Developer Server. Nothing to install.
search_devdocs 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_devdocs 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_devdocs. 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_devdocs is provided by the MCP Developer Server MCP server (ra86-dev/mcpdev-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →