This record as markdown: /tools/browser/get-tab-content-text.md
What get_tab_content_text does on Browser
AI agents call get_tab_content_text to retrieve information from Browser without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_tab_content_text is rated Low
This tool queries and retrieves the text content from a browser tab without modifying, executing, or deleting anything. It is a read-only operation with minimal blast radius. Even if misused by an agent, it only exposes information already visible in the browser and poses no risk of unintended side effects, financial harm, or data destruction.
From the tool's definition Tool name and description indicate retrieval only: 'Get text content of a specific tab' — no mutation, deletion, or execution mentioned.
Attacks that exploit this kind of access
The rule that runs get_tab_content_text safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Browser, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_tab_content_text, this is the rule to start with:
get_tab_content_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 Browser, apply this rule, and every get_tab_content_text call is checked against it from then on.
Questions about get_tab_content_text
Get text content of a specific tab. It is categorised as a Read tool in the Browser MCP Server, which means it retrieves data without modifying state.
Register the Browser MCP server in PolicyLayer and add a rule for get_tab_content_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 Browser. Nothing to install.
get_tab_content_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_content_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_content_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_content_text is provided by the Browser MCP server (mcp-server-browser). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Browser, and thousands of servers like it.
This server
Across the catalogue