browser_profile_save

THE RISK

Medium Risk

Why browser_profile_save needs a policy

This tool creates or modifies browser profile data by persistently storing cookies, localStorage, and URL information. This is a Write operation—it produces reversible state changes (profiles can be overwritten or deleted).

From the tool's definition Tool description states 'Save current browser state (cookies + localStorage + URL) as a profile.' The verb 'save' indicates persistent storage creation/modification of browser state data.

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

POLICY

How to control browser_profile_save

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_profile_save:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_profile_save": {
      "limits": [
        {
          "counter": "browser_profile_save_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

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.

LIMIT 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 →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about browser_profile_save

What does the browser_profile_save tool do? +

Save current browser state (cookies + localStorage + URL) as a profile. 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.

How do I enforce a policy on browser_profile_save? +

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

browser_profile_save is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit browser_profile_save? +

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

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

browser_profile_save 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 →