List every open tab in the controlled Chrome (id, title, url, active) — the real browser, not just bridge-connected tabs. Requires chrome_launch first (or an already-debuggable Chrome on --chrome-port).
AI agents call chrome_tabs 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.
This is a read-only tool that enumerates browser tabs for inspection purposes. It gathers data about the state of the controlled Chrome instance without modifying anything. The blast radius from misuse is minimal—leaking the browser state is a data confidentiality concern but not a capability to cause destructive action or external harm.
From the tool's definition Tool description explicitly states it 'List[s] every open tab' and retrieves 'id, title, url, active' — purely informational queries with no side effects. No modification, deletion, or command execution occurs.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List every open tab in the controlled Chrome (id, title, url, active) — the real browser, not just bridge-connected tabs. Requires chrome_launch first (or an already-debuggable Chrome on --chrome-port). 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 chrome_tabs: 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.
chrome_tabs 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 chrome_tabs 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 chrome_tabs. 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.
chrome_tabs 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 →