Clear all captured DOM mutations.
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.
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
Documented attack patterns abuse exactly the kind of access browser_mutations_clear gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Termux Browser Pilot, and nothing reaches the server without passing your rules. This is the rule we recommend for browser_mutations_clear:
{
"version": "1",
"default": "deny",
"hide": [
"browser_mutations_clear"
]
}browser_mutations_clear disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
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.
Start from Termux Browser Pilot, 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.
148 Termux Browser Pilot tools catalogued and risk-classified — across an index of 43,000+ MCP servers.