chrome_read_tab

SERVERLocal SOURCElocal-mcp

Low RISK CLASS

Category Read

Parameters 60 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-local-mcp-local-mcp/chrome-read-tab.md

WHAT IT DOES

What chrome_read_tab does on Local

AI agents call chrome_read_tab to retrieve information from Local without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`max_bytes`	integer	—	Max bytes of text (and html) to return (default 102400)
`tab_index`	integer	—	Tab index from chrome_list_tabs (default active tab of that window)
`url_match`	string	—	Substring to match against the tab URL. Takes precedence over indices.
`include_html`	boolean	—	Also return the HTML source (default false)
`window_index`	integer	—	Window index from chrome_list_tabs (default 0)
`include_links`	boolean	—	Extract all links with href + visible text (default false). Great for navigating SPAs.

Parameters from the server's own tool schema.

RISK

Why chrome_read_tab is rated Low

This is fundamentally a read operation that retrieves and queries rendered page content from a browser tab. It has no side effects on the browser state or external systems beyond passive data extraction.

From the tool's definition Tool name 'chrome_read_tab' and description 'Reads the rendered text content of a Google Chrome tab.' The function retrieves data (text content, HTML source, links) with options for `include_html` and `include_links`, and explicitly states 'Text is capped at…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs chrome_read_tab safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For chrome_read_tab, this is the rule to start with:

chrome_read_tab Allowed

chrome_read_tab is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "chrome_read_tab": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every chrome_read_tab call is checked against it from then on.

FAQ

Questions about chrome_read_tab

What does the chrome_read_tab tool do? +

Reads the rendered text content of a Google Chrome tab. Identify the tab either by url_match (substring match against URL; first hit wins) or by window_index + tab_index (from chrome_list_tabs). Text is capped at max_bytes (default 100 KB). Pass include_html: true to also get the raw HTML source. Pass include_links: true to extract all links with their href and text. Requires 'Allow JavaScript from Apple Events' (Chrome → View → Developer); run chrome_setup_check if reads come back empty. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.

What parameters does chrome_read_tab accept? +

chrome_read_tab accepts 6 parameters: max_bytes, tab_index, url_match, include_html, window_index, include_links. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on chrome_read_tab? +

Register the Local MCP server in PolicyLayer and add a rule for chrome_read_tab: 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 Local. Nothing to install.

What risk level is chrome_read_tab? +

chrome_read_tab is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit chrome_read_tab? +

Yes. Add a rate_limit block to the chrome_read_tab 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.

How do I block chrome_read_tab completely? +

Set action: deny in the PolicyLayer policy for chrome_read_tab. 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.

What MCP server provides chrome_read_tab? +

chrome_read_tab is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Local, and thousands of servers like it.

This server

All 234 Local tools →

Across the catalogue

claude_read_file on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →