Use this when investigating performance issues or excessive re-renders. Returns stores ranked by activity — frequent changes, many action calls — to pinpoint bottlenecks. Example: {limit: 10} or {windowMs: 30000, compact: true}.
AI agents call nanostores_find_noisy_stores 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 |
|---|---|---|---|
limit | number | — | Number of stores to return |
compact | boolean | — | Return TOON-encoded compact table for lower token cost |
windowMs | number | — | Time window in milliseconds (from now back) |
Parameters from the server's own tool schema.
This is a monitoring and analysis tool for debugging performance issues. It queries runtime metrics and returns ranked results for investigation purposes. There are no side effects, state changes, or destructive operations — it purely retrieves observability data about the Nanostores runtime, making it a Read operation with low risk if misused.
From the tool's definition Tool returns data about store activity and re-render metrics ('ranked by activity', 'frequent changes', 'many action calls') without modifying, deleting, or executing anything.
Attacks that exploit this kind of access
Use this when investigating performance issues or excessive re-renders. Returns stores ranked by activity — frequent changes, many action calls — to pinpoint bottlenecks. Example: {limit: 10} or {windowMs: 30000, compact: true}. It is categorised as a Read tool in the Nanostores MCP MCP Server, which means it retrieves data without modifying state.
nanostores_find_noisy_stores accepts 3 parameters: limit, compact, windowMs. 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_find_noisy_stores: 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_find_noisy_stores 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_find_noisy_stores 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_find_noisy_stores. 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_find_noisy_stores 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 →