browser_dialog_logs

THE RISK

Low Risk

Why browser_dialog_logs needs a policy

This tool retrieves historical dialog messages (alert/confirm/prompt) that were captured during browser interactions. It performs no modifications, deletions, code execution, or external operations.

From the tool's definition Tool name is 'browser_dialog_logs' and description states 'Get captured dialog messages' — the verb 'Get' and the read-only nature of retrieving previously captured logs indicates pure data retrieval with no side effects.

Documented attack patterns abuse exactly the kind of access browser_dialog_logs gives an agent:

POLICY

How to control browser_dialog_logs

PolicyLayer is an MCP gateway — it sits between your AI agents and Termux Browser Pilot, and nothing reaches the server without passing your rules. This is the rule we recommend for browser_dialog_logs:

policy.json

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

browser_dialog_logs is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Termux Browser Pilot — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Termux Browser Pilot tools

Destructive browser_auth_delete Delete a saved auth session. Destructive browser_console_clear Clear all captured console log messages. Destructive browser_cookies_clear Clear all browser cookies. Destructive browser_dialog_clear Clear all captured dialog messages. Destructive browser_events_clear Clear all captured DOM events. Destructive browser_headers_clear Clear all custom HTTP headers and remove fetch/XHR hooks. Destructive browser_mock_clear Remove response mock(s). Destructive browser_mutations_clear Clear all captured DOM mutations.

All 148 Termux Browser Pilot tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about browser_dialog_logs

What does the browser_dialog_logs tool do? +

Get captured dialog messages (alert/confirm/prompt). 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_dialog_logs? +

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

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

Can I rate-limit browser_dialog_logs? +

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

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

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

Enforce policy on every Termux Browser Pilot tool call.

Start from Termux Browser Pilot, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →