Click an element by CSS selector, firing a real pointer+mouse+click sequence so React/MUI handlers run. Requires a connected tab.
AI agents invoke click to trigger actions in Nextjs Agent. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers real browser interactions (pointer, mouse, click events) that execute JavaScript event handlers in a live application. The effects depend entirely on what element is clicked — could submit forms, trigger navigation, modify state, invoke APIs, or cause destructive actions. This is Execute-level risk with high severity due to the broad blast radius of arbitrary DOM interaction in a running app.
From the tool's definition 'Click an element by CSS selector, firing a real pointer+mouse+click sequence so React/MUI handlers run'
Attacks that exploit this kind of access
Click an element by CSS selector, firing a real pointer+mouse+click sequence so React/MUI handlers run. Requires a connected tab. It is categorised as a Execute tool in the Nextjs Agent MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Nextjs Agent MCP server in PolicyLayer and add a rule for click: 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.
click is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the click 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 click. 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.
click 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 →