Find Nanostores documentation by topic or store kind. Use query for free-text search across guides, API references, and best practices. Use storeKind to get docs relevant to a specific store type (atom, map, computed, etc.). Combine both to search within store-relevant pages. To read full page co...
AI agents call nanostores_docs_search to retrieve information from Nanostores MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
tags | array | — | Filter by tags (e.g., ['react', 'persistent']) |
limit | number | — | Maximum number of results |
query | string | — | Search query for documentation. Required unless storeKind is provided. |
storeKind | string | — | Find docs relevant to this store type. Can be used alone or with query. |
Parameters from the server's own tool schema.
This tool retrieves and searches documentation content. It performs read-only operations (search, find, get) against documentation resources with no ability to modify, delete, or execute code. The worst-case misuse would be an AI reading documentation it shouldn't have access to, which has minimal blast radius.
From the tool's definition Tool description states "Find Nanostores documentation by topic or store kind" and "Use query for free-text search across guides, API references, and best practices." The action is purely informational retrieval with no side effects.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
Find Nanostores documentation by topic or store kind. Use query for free-text search across guides, API references, and best practices. Use storeKind to get docs relevant to a specific store type (atom, map, computed, etc.). Combine both to search within store-relevant pages. To read full page content, use the nanostores://docs/page/{id} resource. Example: {query: "persistent storage"} or {storeKind: "computed"} or {query: "batched", storeKind: "computed"}. It is categorised as a Read tool in the Nanostores MCP MCP Server, which means it retrieves data without modifying state.
nanostores_docs_search accepts 4 parameters: tags, limit, query, storeKind. The full parameter table on this page comes from the server's own tool schema.
Register the Nanostores MCP server in PolicyLayer and add a rule for nanostores_docs_search: 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 Nanostores MCP. Nothing to install.
nanostores_docs_search 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 nanostores_docs_search 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 nanostores_docs_search. 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.
nanostores_docs_search is provided by the Nanostores MCP server (nanostores-mcp). 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 →