browser_use_profile

Opt in to using a login-capable browser profile (default: isolated profile). Risk 3.

SERVERLocalAnt SOURCEyuga-hashimoto/localant

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/yuga-hashimoto-localant/browser-use-profile.md

WHAT IT DOES

What browser_use_profile does on LocalAnt

AI agents call browser_use_profile to retrieve information from LocalAnt 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_use_profile is rated Low

Even though browser_use_profile only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs browser_use_profile safely

PolicyLayer is an MCP gateway: it sits between your AI agents and LocalAnt, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_use_profile, this is the rule to start with:

browser_use_profile Allowed

browser_use_profile 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_use_profile": {}
  }
}

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

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

FAQ

Questions about browser_use_profile

What does the browser_use_profile tool do? +

Opt in to using a login-capable browser profile (default: isolated profile). Risk 3. It is categorised as a Read tool in the LocalAnt MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on browser_use_profile? +

Register the LocalAnt MCP server in PolicyLayer and add a rule for browser_use_profile: 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 LocalAnt. Nothing to install.

What risk level is browser_use_profile? +

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

Can I rate-limit browser_use_profile? +

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

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

browser_use_profile is provided by the LocalAnt MCP server (yuga-hashimoto/localant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on LocalAnt, and thousands of servers like it.

This server

All 216 LocalAnt tools →

Across the catalogue

The MCP Attack Database →

Guides

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