List all available browser tabs that can be connected to
AI agents call browser_list_tabs to retrieve information from Browser Connect without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about open browser tabs without modifying state, executing commands, or affecting system resources. It is a simple enumeration operation that falls squarely into the Read category. Severity is low because listing tabs poses minimal risk — it only exposes metadata about which pages are loaded, without accessing sensitive data or triggering actions.
From the tool's definition Tool description states 'List all available browser tabs' — a retrieval operation with no modification, deletion, or execution of code. The verb 'list' is a passive read operation.
Documented attack patterns abuse exactly the kind of access browser_list_tabs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Browser Connect, and nothing reaches the server without passing your rules. This is the rule we recommend for browser_list_tabs:
{
"version": "1",
"default": "deny",
"tools": {
"browser_list_tabs": {}
}
} browser_list_tabs is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all available browser tabs that can be connected to. It is categorised as a Read tool in the Browser Connect MCP Server, which means it retrieves data without modifying state.
Register the Browser Connect MCP server in PolicyLayer and add a rule for browser_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 Browser Connect. Nothing to install.
browser_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 browser_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 browser_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.
browser_list_tabs is provided by the Browser Connect MCP server (perception30/browser-connect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Browser Connect, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
16 Browser Connect tools catalogued and risk-classified — across an index of 43,000+ MCP servers.