browser_install

THE RISK

High Risk

Why browser_install needs a policy

This tool installs software (a browser) in the cloud execution environment. Installation is an execution-type operation that modifies the system state by deploying a new application. It is not purely destructive, financial, or a simple read/write of data, but it does trigger an external operation (software installation) whose effects depend on the configuration provided.

From the tool's definition Install the browser specified in the config. Call this if you get an error about the browser not being installed.

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

POLICY

How to control browser_install

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_install": {
      "limits": [
        {
          "counter": "browser_install_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

browser_install stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

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

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Wuying AgentBay tools

Destructive browser_close Close the page Destructive browser_tab_close Close a tab Destructive close_window Close a specific window by its window ID. Destructive release_resource release resource when task finished Execute browser_navigate Navigate to a URL Execute browser_navigate_back Go back to the previous page Execute browser_navigate_forward Go forward to the next page Execute browser_tab_new Open a new tab

All 59 Wuying AgentBay tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Wuying AgentBay → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about browser_install

What does the browser_install tool do? +

Install the browser specified in the config. Call this if you get an error about the browser not being installed. It is categorised as a Execute tool in the Wuying AgentBay MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on browser_install? +

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

What risk level is browser_install? +

browser_install is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit browser_install? +

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

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

browser_install is provided by the Wuying AgentBay MCP server (michael98671/agentbay). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Wuying AgentBay tool call.

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

CHECK YOUR STACK →