browser_get_text

Get all visible text from the current page. Restrictions: Extracts only text content, ignoring HTML tags. Valid: Get the text content of the current page for summarization. Invalid: Get the page

Server Scrapeless Ai Scrapeless @iflow-mcp/scrapeless-ai-scrapeless-mcp-server
Category Read
Risk class Low
Parameters 00 required

What browser_get_text does on Scrapeless Ai Scrapeless

AI agents call browser_get_text to retrieve information from Scrapeless Ai Scrapeless without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why browser_get_text needs a policy

This tool performs a passive information retrieval operation—extracting visible text from a webpage. It has no side effects, cannot execute code, modify data, or trigger external operations. The restriction explicitly confirms it only extracts text content.

From the tool's definition Tool name 'browser_get_text' and description 'Get all visible text from the current page' with explicit restriction 'Extracts only text content, ignoring HTML tags' indicates a read-only operation that retrieves data without modifying or executing actions.

Questions about browser_get_text

What does the browser_get_text tool do? +

Get all visible text from the current page. Restrictions: Extracts only text content, ignoring HTML tags. Valid: Get the text content of the current page for summarization. Invalid: Get the page. It is categorised as a Read tool in the Scrapeless Ai Scrapeless MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on browser_get_text? +

Register the Scrapeless Ai Scrapeless MCP server in PolicyLayer and add a rule for browser_get_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 Scrapeless Ai Scrapeless. Nothing to install.

What risk level is browser_get_text? +

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

Can I rate-limit browser_get_text? +

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

How do I block browser_get_text completely? +

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

What MCP server provides browser_get_text? +

browser_get_text is provided by the Scrapeless Ai Scrapeless MCP server (@iflow-mcp/scrapeless-ai-scrapeless-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

browser_get_text is one line of Scrapeless Ai Scrapeless's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.