browser_useragent_set
Override navigator.userAgent (JS-side). Re-injected after navigation.
This record as markdown: /tools/salviz-termux-browser-pilot/browser-useragent-set.md
What browser_useragent_set does on Termux Browser Pilot
AI agents invoke browser_useragent_set to trigger actions in Termux Browser Pilot. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why browser_useragent_set is rated High
This tool modifies browser behavior by overriding the JavaScript navigator.userAgent property and re-injecting it after each navigation. This is an Execute-class action because it runs JavaScript-side injection that actively manipulates the browser environment on an ongoing basis, affecting how web servers and scripts identify the client.
From the tool's definition Override navigator.userAgent (JS-side). Re-injected after navigation.
Attacks that exploit this kind of access
The rule that runs browser_useragent_set 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_useragent_set, this is the rule to start with:
browser_useragent_set stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Termux Browser Pilot, apply this rule, and every browser_useragent_set call is checked against it from then on.
Questions about browser_useragent_set
Override navigator.userAgent (JS-side). Re-injected after navigation. It is categorised as a Execute tool in the Termux Browser Pilot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Termux Browser Pilot MCP server in PolicyLayer and add a rule for browser_useragent_set: 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_set is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the browser_useragent_set 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_set. 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_set 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