get_tab_text
Extract the plain body text content of a loaded browser tab using scripting. This allows reading and analyzing tab contents (e.g. for summarization or classification). Note: Fails on restricted internal browser pages (e.g., chrome://, edge://, or extensions) or if the tab is not loaded.
This record as markdown: /tools/2manytabs-mcp-host/get-tab-text.md
What get_tab_text does on 2manytabs Mcp Host
AI agents call get_tab_text to retrieve information from 2manytabs Mcp Host 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 |
|---|---|---|---|
tab_id | integer | Yes | The numeric ID of the tab whose body text to extract. |
Parameters from the server's own tool schema.
Why get_tab_text is rated Low
Even though get_tab_text only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs get_tab_text safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 2manytabs Mcp Host, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_tab_text, this is the rule to start with:
get_tab_text is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 2manytabs Mcp Host, apply this rule, and every get_tab_text call is checked against it from then on.
Questions about get_tab_text
Extract the plain body text content of a loaded browser tab using scripting. This allows reading and analyzing tab contents (e.g. for summarization or classification). Note: Fails on restricted internal browser pages (e.g., chrome://, edge://, or extensions) or if the tab is not loaded. It is categorised as a Read tool in the 2manytabs Mcp Host MCP Server, which means it retrieves data without modifying state.
get_tab_text accepts 1 parameter: tab_id. Required: tab_id. The full parameter table on this page comes from the server's own tool schema.
Register the 2manytabs Mcp Host MCP server in PolicyLayer and add a rule for get_tab_text: 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 2manytabs Mcp Host. Nothing to install.
get_tab_text 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_tab_text 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_tab_text. 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_tab_text is provided by the 2manytabs Mcp Host MCP server (2manytabs-mcp-host). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 2manytabs Mcp Host, and thousands of servers like it.
This server
Across the catalogue