Returns the complete store/subscriber/relation index for the project. Use compact:true for a token-efficient directory-level overview (store counts by folder). Use the full mode (default) when you need to iterate over every entity or build a complete picture. Example: {compact: true} for director...
AI agents call nanostores_scan_project 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 |
|---|---|---|---|
force | boolean | — | Force a fresh scan, bypassing the cache. |
compact | boolean | — | Return a compact directory-level summary instead of full store/subscriber lists. Use when you need a token-efficient overview of where stores live, not individu |
rootUri | string | — |
Parameters from the server's own tool schema.
nanostores_scan_project is a diagnostic/analysis tool that scans and indexes project state without side effects. It reads Nanostore configuration and structure to support debugging. The parameters (compact, force) only control output format and caching, not the underlying operation. This is purely a Read operation with minimal risk — an AI agent using it cannot modify stores, execute code, or cause damage.
From the tool's definition Tool description states it 'Returns the complete store/subscriber/relation index' and supports 'directory-level overview' and 'iterate over every entity' — these are information retrieval operations with no modification, deletion, or execution of code.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Returns the complete store/subscriber/relation index for the project. Use compact:true for a token-efficient directory-level overview (store counts by folder). Use the full mode (default) when you need to iterate over every entity or build a complete picture. Example: {compact: true} for directory overview, {force: true} to bypass cache. It is categorised as a Read tool in the Nanostores MCP MCP Server, which means it retrieves data without modifying state.
nanostores_scan_project accepts 3 parameters: force, compact, rootUri. 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_scan_project: 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_scan_project 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_scan_project 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_scan_project. 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_scan_project 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 →