Get HTML content from the page or a specific element.
AI agents call browser_get_html to retrieve information from Daytona Playwright MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and returns HTML content without modifying, creating, deleting, or executing any operations. It is a read-only query of the current DOM state. Even though it operates within a browser sandbox environment controlled via MCP, the action itself causes no state changes or external effects beyond data retrieval.
From the tool's definition Tool name is 'browser_get_html' and description states it 'Get[s] HTML content from the page or a specific element.' This is purely a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get HTML content from the page or a specific element. It is categorised as a Read tool in the Daytona Playwright MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Daytona Playwright MCP Server 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 Daytona Playwright MCP Server. 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 Daytona Playwright MCP Server MCP server (jamesmurdza/playwright-daytona-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 →