browser_mutations_clear
Clear all captured DOM mutations.
This record as markdown: /tools/salviz-termux-browser-pilot/browser-mutations-clear.md
What browser_mutations_clear does on Termux Browser Pilot
AI agents call browser_mutations_clear to permanently remove resources in Termux Browser Pilot, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why browser_mutations_clear is rated Critical
Clearing captured DOM mutations is an irreversible action that destroys recorded observation data. While it doesn't delete files or external data, the captured mutation history cannot be recovered once cleared, making it Destructive. Severity is medium since it affects in-memory/session data rather than persistent storage.
From the tool's definition 'Clear all captured DOM mutations' — permanently removes/clears recorded mutation data
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs browser_mutations_clear safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Termux Browser Pilot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_mutations_clear, this is the rule to start with:
browser_mutations_clear is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Termux Browser Pilot, apply this rule, and every browser_mutations_clear call is checked against it from then on.
Questions about browser_mutations_clear
Clear all captured DOM mutations. It is categorised as a Destructive tool in the Termux Browser Pilot MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Termux Browser Pilot MCP server in PolicyLayer and add a rule for browser_mutations_clear: 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 Termux Browser Pilot. Nothing to install.
browser_mutations_clear is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the browser_mutations_clear 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_mutations_clear. 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_mutations_clear is provided by the Termux Browser Pilot MCP server (salviz/termux-browser-pilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Termux Browser Pilot, and thousands of servers like it.
Across the catalogue