Find the version-accurate Next.js documentation for THIS project. This tool does NOT fetch documentation. Next.js 16+ ships its full docs inside the installed package at node_modules/next/dist/docs/ (markdown), kept in sync with the exact version you have installed. This tool tells you where thos...
AI agents call nextjs_docs to retrieve information from Next Devtools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
topic | string | — | |
project_path | string | — |
Parameters from the server's own tool schema.
The tool locates and provides pointers to local documentation files within the project's node_modules directory. It performs a read-only lookup operation with no side effects, no data modification, no code execution, and no irreversible actions. The low severity reflects minimal blast radius if misused by an agent — worst case is providing incorrect documentation paths, which causes user confusion but no system harm.
From the tool's definition Tool description states it 'tells you where those docs are and how to read them' and 'Find the version-accurate Next.js documentation' — this is purely informational retrieval of file paths and documentation metadata with no modification, deletion, or…
Attacks that exploit this kind of access
Find the version-accurate Next.js documentation for THIS project. This tool does NOT fetch documentation. Next.js 16+ ships its full docs inside the installed package at node_modules/next/dist/docs/ (markdown), kept in sync with the exact version you have installed. This tool tells you where those docs are and how to read them — so you read the docs that match this project, not a generic or outdated copy. Call this before answering Next.js questions or writing Next.js code. Then read the relevant guide from the path it returns. If the project is on an older Next.js, it will tell you how to upgrade. It is categorised as a Read tool in the Next Devtools MCP Server, which means it retrieves data without modifying state.
nextjs_docs accepts 2 parameters: topic, project_path. The full parameter table on this page comes from the server's own tool schema.
Register the Next Devtools MCP server in PolicyLayer and add a rule for nextjs_docs: 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 Next Devtools. Nothing to install.
nextjs_docs 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 nextjs_docs 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 nextjs_docs. 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.
nextjs_docs is provided by the Next Devtools MCP server (next-devtools-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 →