browser_audit
One-command page health report.
This record as markdown: /tools/salviz-termux-browser-pilot/browser-audit.md
What browser_audit does on Termux Browser Pilot
AI agents call browser_audit 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.
Why browser_audit is rated Low
A page health report is a read-only operation that gathers and presents information about the current state of a web page (performance metrics, accessibility issues, etc.). It performs no mutations, executions of external code, financial operations, or destructive actions. The tool fits squarely into the Read category as it queries and retrieves data with no side effects.
From the tool's definition Tool name 'browser_audit' and description 'One-command page health report' indicate a diagnostic/auditing function that retrieves and reports on page state without modifying it.
Attacks that exploit this kind of access
The rule that runs browser_audit 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_audit, this is the rule to start with:
browser_audit is read-only, so it stays allowed. 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_audit call is checked against it from then on.
Questions about browser_audit
One-command page health report. It is categorised as a Read tool in the Termux Browser Pilot MCP Server, which means it retrieves data without modifying state.
Register the Termux Browser Pilot MCP server in PolicyLayer and add a rule for browser_audit: 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_audit is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the browser_audit 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_audit. 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_audit 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