List every browser tab connected to the broker: each tab\
AI agents call list_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 tool performs a read-only operation that retrieves the state of browser tabs. There are no side effects, no code execution, no data modification or deletion, and no financial implications. The blast radius of misuse is minimal—an agent could only gain visibility into which tabs are open, which does not enable harmful actions by itself. This is a straightforward Read category tool.
From the tool's definition Tool name 'list_tabs' and description 'List every browser tab connected to the broker: each tab' indicate a query/enumeration operation that retrieves information about open browser tabs without modifying, deleting, or executing actions on them.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List every browser tab connected to the broker: each 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 list_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.
list_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 list_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 list_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.
list_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 →