browser_search

Find text on the page and highlight all matches.

SERVERTermux Browser Pilot SOURCEsalviz/termux-browser-pilot

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What browser_search does on Termux Browser Pilot

AI agents call browser_search to retrieve information from Termux Browser Pilot without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why browser_search is rated Low

browser_search performs text discovery and visual highlighting within the current page context. This is a passive information retrieval operation with no capability to modify page state, execute actions, delete data, or trigger external operations. The highlighting is purely a UI affordance for the user/agent to locate information.

From the tool's definition Tool description states 'Find text on the page and highlight all matches' - a read-only operation that searches and displays existing content without modifying data, executing code, or causing side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs browser_search 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_search, this is the rule to start with:

browser_search Allowed

browser_search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_search": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Termux Browser Pilot, apply this rule, and every browser_search call is checked against it from then on.

FAQ

Questions about browser_search

What does the browser_search tool do? +

Find text on the page and highlight all matches. It is categorised as a Read tool in the Termux Browser Pilot MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on browser_search? +

Register the Termux Browser Pilot MCP server in PolicyLayer and add a rule for browser_search: 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_search? +

browser_search is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit browser_search? +

Yes. Add a rate_limit block to the browser_search 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_search completely? +

Set action: deny in the PolicyLayer policy for browser_search. 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_search? +

browser_search 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.

KEEP EXPLORING

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

This server

All 148 Termux Browser Pilot tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →search_circuits on 0gzk → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →