Use this when you need details about a specific store — its kind, file location, direct subscribers, and first-level derived relations. Accepts store id or name. For multi-hop dependency chains use nanostores_store_subgraph instead. Example: {name: "$counter"} or {storeId: "store:src/stores.ts#$c...
AI agents call nanostores_store_summary 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 |
|---|---|---|---|
file | string | — | Optional relative file path to disambiguate store name. |
name | string | — | Store name. Used if storeId is not provided. |
rootUri | string | — | Project root URI or path for multi-root setups; defaults to first root. |
storeId | string | — | Exact store id. If provided, takes priority. |
Parameters from the server's own tool schema.
This tool performs a query operation to fetch and display store metadata and dependency information. It has no side effects, cannot modify data, and cannot execute code or commands. The capability is purely exploratory/analytical, consistent with the server's stated purpose of 'debug and analyze Nanostores apps.' This is a straightforward Read category tool with minimal risk.
From the tool's definition Tool retrieves details about a specific store including 'its kind, file location, direct subscribers, and first-level derived relations.' The verb 'get details' and the informational nature of the returned data (store metadata, relationships) indicate data…
Risk signalsAccepts file system path (file)
Attacks that exploit this kind of access
Use this when you need details about a specific store — its kind, file location, direct subscribers, and first-level derived relations. Accepts store id or name. For multi-hop dependency chains use nanostores_store_subgraph instead. Example: {name: "$counter"} or {storeId: "store:src/stores.ts#$counter"}. It is categorised as a Read tool in the Nanostores MCP MCP Server, which means it retrieves data without modifying state.
nanostores_store_summary accepts 4 parameters: file, name, rootUri, storeId. 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_store_summary: 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_store_summary 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_store_summary 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_store_summary. 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_store_summary 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 →