Returns HTML source of current page (truncated to 5000 chars).
AI agents call dom_get_source to retrieve information from Browser-Debugger without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns the HTML source code of the currently loaded webpage. It performs no modifications, deletions, or execution of code—it simply reads and returns existing data. While an AI agent could use this to discover sensitive information in page markup, the tool itself is fundamentally a read operation with no destructive or executable capabilities.
From the tool's definition Tool name 'dom_get_source' and description 'Returns HTML source of current page' indicate data retrieval with no modification or side effects. The truncation to 5000 characters confirms it is a read-only operation.
Documented attack patterns abuse exactly the kind of access dom_get_source gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Browser-Debugger, and nothing reaches the server without passing your rules. This is the rule we recommend for dom_get_source:
{
"version": "1",
"default": "deny",
"tools": {
"dom_get_source": {}
}
}dom_get_source is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Returns HTML source of current page (truncated to 5000 chars). It is categorised as a Read tool in the Browser-Debugger MCP Server, which means it retrieves data without modifying state.
Register the Browser-Debugger MCP server in PolicyLayer and add a rule for dom_get_source: 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-Debugger. Nothing to install.
dom_get_source 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 dom_get_source 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 dom_get_source. 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.
dom_get_source is provided by the Browser-Debugger MCP server (selvadinesh-giga/mcp-based-browser-debug-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Browser-Debugger, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
14 Browser-Debugger tools catalogued and risk-classified — across an index of 43,000+ MCP servers.