search_docs
Full-text search across the product documentation. Returns the best-matching pages with title, description, canonical URL, matched section headings, and a snippet. Omit product to search every product at once, or pass one of the ids from list_products to scope it.
This record as markdown: /tools/com-freebatteryfactory-docs/search-docs.md
What search_docs does on Docs
AI agents call search_docs to retrieve information from Docs 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 |
|---|---|---|---|
limit | integer | — | Maximum results to return (default 8, max 25). |
query | string | Yes | Search terms, e.g. "boundary hysteresis" or "deterministic replay". |
product | string | — | Optional product id from list_products to scope the search. Omit to search all products. |
Parameters from the server's own tool schema.
Why search_docs is rated Low
search_docs is a query/search operation that retrieves documentation without side effects. It does not create, modify, delete, or execute code. The only parameters are search scope filters (product selection), which constrain what data is returned rather than alter any state. This is a canonical Read operation with minimal security risk.
From the tool's definition Tool performs 'Full-text search' and 'Returns the best-matching pages' with no modification or deletion capabilities. The description explicitly indicates retrieval only ('read the Free Battery Factory docs').
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs search_docs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Docs, 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 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 Docs, apply this rule, and every search_docs call is checked against it from then on.
Questions about search_docs
Full-text search across the product documentation. Returns the best-matching pages with title, description, canonical URL, matched section headings, and a snippet. Omit product to search every product at once, or pass one of the ids from list_products to scope it. It is categorised as a Read tool in the Docs MCP Server, which means it retrieves data without modifying state.
search_docs accepts 3 parameters: limit, query, product. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Docs 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 Docs. Nothing to install.
search_docs 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_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.
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.
search_docs is provided by the Docs MCP server (https://freebatteryfactory.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Docs, and thousands of servers like it.
This server
Across the catalogue