Get detailed information about a specific TanStack Start add-on (files, dependencies, options, routes)
AI agents call getAddOnDetails to retrieve information from TanStack MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns structured information (files, dependencies, options, routes) about an existing add-on. It has no side effects, does not execute code, create resources, modify data, or delete anything. It is purely informational/read-only access to documentation or metadata.
From the tool's definition Tool description states 'Get detailed information about a specific TanStack Start add-on' - this is a retrieval operation that queries and returns data about add-ons without modifying or executing anything.
Attacks that exploit this kind of access
Get detailed information about a specific TanStack Start add-on (files, dependencies, options, routes). It is categorised as a Read tool in the TanStack MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TanStack MCP Server MCP server in PolicyLayer and add a rule for getAddOnDetails: 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 MCP Server. Nothing to install.
getAddOnDetails 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 getAddOnDetails 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 getAddOnDetails. 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.
getAddOnDetails is provided by the TanStack MCP Server MCP server (zpeppoz/tanstack-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 →