Clear user agent override (restore original navigator.userAgent).
AI agents use browser_useragent_clear to create or update resources in Termux Browser Pilot — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Termux Browser Pilot environment.
This tool modifies browser configuration by clearing/resetting the user agent override back to its original value. It's a reversible configuration change (Write category), not destructive since it restores rather than permanently removes data. The blast radius is low as it only affects how the browser identifies itself to web servers.
From the tool's definition Clear user agent override (restore original navigator.userAgent)
Documented attack patterns abuse exactly the kind of access browser_useragent_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_useragent_clear:
{
"version": "1",
"default": "deny",
"tools": {
"browser_useragent_clear": {
"limits": [
{
"counter": "browser_useragent_clear_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}browser_useragent_clear stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Clear user agent override (restore original navigator.userAgent). It is categorised as a Write tool in the Termux Browser Pilot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Termux Browser Pilot MCP server in PolicyLayer and add a rule for browser_useragent_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_useragent_clear is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the browser_useragent_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_useragent_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_useragent_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.