browser_highlight_clear
Remove element highlights.
This record as markdown: /tools/salviz-termux-browser-pilot/browser-highlight-clear.md
What browser_highlight_clear does on Termux Browser Pilot
AI agents use browser_highlight_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_highlight_clear is rated Medium
Clearing/removing visual highlights modifies the state of the browser UI (reversibly), but has minimal blast radius as it only affects visual presentation with no data loss or external effects.
From the tool's definition Remove element highlights
Attacks that exploit this kind of access
The rule that runs browser_highlight_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_highlight_clear, this is the rule to start with:
browser_highlight_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Termux Browser Pilot, apply this rule, and every browser_highlight_clear call is checked against it from then on.
Questions about browser_highlight_clear
Remove element highlights. 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_highlight_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_highlight_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_highlight_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_highlight_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_highlight_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.
This server
Across the catalogue