browser_get_dom
Get the full page HTML (truncated to 50KB). Use to understand page structure when screenshots aren't enough — find element selectors, form fields, buttons, etc.
This record as markdown: /tools/io-github-kivanccakmak-yaver/browser-get-dom.md
What browser_get_dom does on Yaver
AI agents call browser_get_dom to retrieve information from Yaver 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 |
|---|---|---|---|
session_id | string | Yes | Session ID |
Parameters from the server's own tool schema.
Why browser_get_dom is rated Low
This tool retrieves data (HTML DOM content) for inspection purposes only. It performs no modifications, deletions, executions, or financial operations. The 50KB truncation limit and read-only nature confirm it is a safe inspection tool. Severity is low because HTML content exposure is typically not sensitive in local dev contexts, and the tool cannot trigger side effects.
From the tool's definition Tool description: 'Get the full page HTML (truncated to 50KB). Use to understand page structure when screenshots aren't enough — find element selectors, form fields, buttons, etc.' The verb 'Get' and explicit purpose of retrieving and reading page structure…
Attacks that exploit this kind of access
The rule that runs browser_get_dom safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_get_dom, this is the rule to start with:
browser_get_dom 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 Yaver, apply this rule, and every browser_get_dom call is checked against it from then on.
Questions about browser_get_dom
Get the full page HTML (truncated to 50KB). Use to understand page structure when screenshots aren't enough — find element selectors, form fields, buttons, etc. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
browser_get_dom accepts 1 parameter: session_id. Required: session_id. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for browser_get_dom: 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 Yaver. Nothing to install.
browser_get_dom 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_dom 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_dom. 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_dom is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue