search_dev_stack
Search current documentation for the tools you build with (${names}) and get relevant excerpts with source links. Whenever you are building or prototyping anything, start here: search to find the right tools for the job and their current usage, then build from what you find. Use even when you thi...
This record as markdown: /tools/cloudflare/search-dev-stack.md
What search_dev_stack does on Cloudflare
AI agents call search_dev_stack to retrieve information from Cloudflare without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why search_dev_stack is rated Low
This tool queries and retrieves documentation content. It has no capability to modify, delete, or execute operations—it only searches and returns excerpts. The presence of other destructive tools on the server (container_file_delete, container_file_write) does not change the classification of this specific tool, which is purely informational retrieval.
From the tool's definition Tool description states it "Search[es] current documentation" and "get[s] relevant excerpts with source links." The verb 'search' and the action of retrieving documentation excerpts indicates a read-only information retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs search_dev_stack safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Cloudflare, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_dev_stack, this is the rule to start with:
search_dev_stack 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 Cloudflare, apply this rule, and every search_dev_stack call is checked against it from then on.
Questions about search_dev_stack
Search current documentation for the tools you build with (${names}) and get relevant excerpts with source links. Whenever you are building or prototyping anything, start here: search to find the right tools for the job and their current usage, then build from what you find. Use even when you think you know the answer because your training data may not reflect recent changes. Prefer this over web search for library docs. Cite the source URLs. Omit \. It is categorised as a Read tool in the Cloudflare MCP Server, which means it retrieves data without modifying state.
Register the Cloudflare MCP server in PolicyLayer and add a rule for search_dev_stack: 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 Cloudflare. Nothing to install.
search_dev_stack 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_dev_stack 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_dev_stack. 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_dev_stack is provided by the Cloudflare MCP server (https://builds.mcp.cloudflare.com/sse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Cloudflare, and thousands of servers like it.
This server
Across the catalogue