Get recent DOM changes (attribute changes, added/removed nodes)
AI agents call get_dom_mutations to retrieve information from Mcp Browser Lens without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the current state of DOM mutations (reads historical changes to the page's DOM structure and attributes). It has no side effects, does not execute code, does not modify data, and does not delete anything. It is purely observational/informational in nature, consistent with Read category tools like 'get' and 'fetch'.
From the tool's definition Tool name 'get_dom_mutations' and description 'Get recent DOM changes (attribute changes, added/removed nodes)' indicate a retrieval operation that observes and reports DOM state changes without modifying or executing operations.
Attacks that exploit this kind of access
Get recent DOM changes (attribute changes, added/removed nodes). It is categorised as a Read tool in the Mcp Browser Lens MCP Server, which means it retrieves data without modifying state.
Register the Mcp Browser Lens MCP server in PolicyLayer and add a rule for get_dom_mutations: 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 Mcp Browser Lens. Nothing to install.
get_dom_mutations 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 get_dom_mutations 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 get_dom_mutations. 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.
get_dom_mutations is provided by the Mcp Browser Lens MCP server (nano-step/mcp-browser-lens). 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 →