Given a CSS selector, return the chain of React components that render that DOM element (nearest owner first), each with its hook shape. Requires a connected tab.
AI agents call component_for to retrieve information from Nextjs Agent without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool reads and returns component hierarchy information for a given DOM element. It performs no writes, executions, or destructive actions — it is purely a read/inspection operation against a running Next.js app's React component tree.
From the tool's definition 'return the chain of React components that render that DOM element... each with its hook shape' — pure introspection/query with no side effects
Attacks that exploit this kind of access
Given a CSS selector, return the chain of React components that render that DOM element (nearest owner first), each with its hook shape. Requires a connected tab. It is categorised as a Read tool in the Nextjs Agent MCP Server, which means it retrieves data without modifying state.
Register the Nextjs Agent MCP server in PolicyLayer and add a rule for component_for: 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 Nextjs Agent. Nothing to install.
component_for 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 component_for 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 component_for. 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.
component_for is provided by the Nextjs Agent MCP server (zohaib3249/nextjs-agent-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 →