Get open tabs from the current local browser session.
AI agents call get_tabs_local to retrieve information from Chromium Sync without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves browser tab information from a local session—a read-only operation. However, the severity is medium rather than low because access to open tabs can reveal sensitive information about user activity, authentication tokens in URLs, personal browsing patterns, or confidential work contexts that could be exploited if an AI agent misuses the data.
From the tool's definition Tool name 'get_tabs_local' and description 'Get open tabs from the current local browser session' indicate data retrieval with no modification. The broader server context shows it 'retrieves or queries data' from browser profiles without authentication.
Attacks that exploit this kind of access
Get open tabs from the current local browser session. It is categorised as a Read tool in the Chromium Sync MCP Server, which means it retrieves data without modifying state.
Register the Chromium Sync MCP server in PolicyLayer and add a rule for get_tabs_local: 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 Chromium Sync. Nothing to install.
get_tabs_local 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 get_tabs_local 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 get_tabs_local. 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.
get_tabs_local is provided by the Chromium Sync MCP server (jaidhyani/chromium-sync-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 →