Fetch the full content of a specific TanStack documentation page
AI agents call tanstack_doc 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 queries documentation content. The verb 'Fetch' and the stated purpose of accessing documentation pages confirm it is a Read operation with no destructive, financial, or code execution capabilities. Severity is low as documentation access poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'tanstack_doc' and description 'Fetch the full content of a specific TanStack documentation page' indicate retrieval of documentation data with no modification or side effects.
Attacks that exploit this kind of access
Fetch the full content of a specific TanStack documentation page. 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 tanstack_doc: 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.
tanstack_doc 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 tanstack_doc 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 tanstack_doc. 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.
tanstack_doc 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 →