List all open Chrome/Electron tabs. Use cdpPort to connect to a specific app (e.g. 9333 for Codex Desktop).
AI agents call browser_tabs to retrieve information from ScreenHand without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs data retrieval only (listing open tabs). It has no side effects, does not execute code or commands, does not modify or delete data, and does not involve financial operations. The highest severity concern would be information disclosure (what tabs are open), which is relatively low-impact for desktop automation contexts.
From the tool's definition Tool name is 'browser_tabs' and description states 'List all open Chrome/Electron tabs' — a read-only operation that retrieves information without modifying state.
Documented attack patterns abuse exactly the kind of access browser_tabs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ScreenHand, and nothing reaches the server without passing your rules. This is the rule we recommend for browser_tabs:
{
"version": "1",
"default": "deny",
"tools": {
"browser_tabs": {}
}
}browser_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 open Chrome/Electron tabs. Use cdpPort to connect to a specific app (e.g. 9333 for Codex Desktop). It is categorised as a Read tool in the ScreenHand MCP Server, which means it retrieves data without modifying state.
Register the ScreenHand MCP server in PolicyLayer and add a rule for browser_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 ScreenHand. Nothing to install.
browser_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_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_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_tabs is provided by the ScreenHand MCP server (manushi4/screenhand). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ScreenHand, 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.
89 ScreenHand tools catalogued and risk-classified — across an index of 43,000+ MCP servers.