Get the full HTML of the current page. Restrictions: Returns the entire raw HTML source code. Valid: Get the HTML of the current page to parse its structure. Invalid: Get only the visible text (use
AI agents call browser_get_html to retrieve information from Scrapeless without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries data (HTML source code) from the currently-loaded browser page with no side effects—no data is modified, deleted, or executed. It is a pure read operation analogous to fetching or querying information. The low severity reflects that HTML retrieval alone poses minimal risk unless the agent misuses the extracted data elsewhere.
From the tool's definition Tool name 'browser_get_html' and description states it 'Get the full HTML of the current page' and 'Returns the entire raw HTML source code.' The valid use case explicitly mentions parsing page structure without modification.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Get the full HTML of the current page. Restrictions: Returns the entire raw HTML source code. Valid: Get the HTML of the current page to parse its structure. Invalid: Get only the visible text (use. It is categorised as a Read tool in the Scrapeless MCP Server, which means it retrieves data without modifying state.
Register the Scrapeless MCP server in PolicyLayer and add a rule for browser_get_html: 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. Nothing to install.
browser_get_html 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 browser_get_html 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 browser_get_html. 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.
browser_get_html is provided by the Scrapeless MCP server (scrapeless-mcp-server). 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 →