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

browser_audit

One-command page health report.

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

Questions about browser_audit

What does the browser_audit tool do? +

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.

How do I enforce a policy on browser_audit? +

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.

What risk level is browser_audit? +

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

Can I rate-limit browser_audit? +

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.

How do I block browser_audit completely? +

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.

What MCP server provides browser_audit? +

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.

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.