Returns query keys, status, staleness, observers, and update times from the connected app.
AI agents call get_query_cache_summary to retrieve information from Tanstack Start Devtools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves internal state information about TanStack Query's cache without modifying any data. It provides diagnostic/observability information for development purposes. The operation is non-destructive and read-only, making it appropriate for the Read category with low severity since cache inspection poses minimal risk even if misused by an agent.
From the tool's definition Tool name 'get_query_cache_summary' and description 'Returns query keys, status, staleness, observers, and update times' indicate data retrieval only.
Attacks that exploit this kind of access
Returns query keys, status, staleness, observers, and update times from the connected app. It is categorised as a Read tool in the Tanstack Start Devtools MCP Server, which means it retrieves data without modifying state.
Register the Tanstack Start Devtools MCP server in PolicyLayer and add a rule for get_query_cache_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 Tanstack Start Devtools. Nothing to install.
get_query_cache_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 get_query_cache_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 get_query_cache_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.
get_query_cache_summary is provided by the Tanstack Start Devtools MCP server (mantrakp04/tanstack-start-dev-tool-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 →