New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

browser_useragent_clear

Clear user agent override (restore original navigator.userAgent).

SERVERTermux Browser Pilot SOURCEsalviz/termux-browser-pilot
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/salviz-termux-browser-pilot/browser-useragent-clear.md

What browser_useragent_clear does on Termux Browser Pilot

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.

Why browser_useragent_clear is rated Medium

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)

Questions about browser_useragent_clear

What does the browser_useragent_clear tool do? +

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.

How do I enforce a policy on browser_useragent_clear? +

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.

What risk level is browser_useragent_clear? +

browser_useragent_clear is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit browser_useragent_clear? +

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.

How do I block browser_useragent_clear completely? +

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.

What MCP server provides browser_useragent_clear? +

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.

More on Termux Browser Pilot, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Termux Browser Pilot's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.