browser_control_media · Browser MCP Server MCP

WHAT IT DOES

What browser_control_media does on Browser MCP Server

AI agents invoke browser_control_media to trigger actions in Browser MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why browser_control_media needs a policy

This tool triggers external operations on media elements in a browser (play, pause, seek, mute). It doesn't merely read data nor does it irreversibly destroy or write persistent data — it executes actions that control the state of a media element. The effects depend on arguments passed (which media element, which action). Misuse could disrupt user sessions or automated workflows but has limited blast radius.

From the tool's definition Control a media element (play, pause, seek, mute)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_control_media Rate-limited

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

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Browser MCP Server, so you can run agents against it safely.

FAQ

Questions about browser_control_media

What does the browser_control_media tool do? +

Control a media element (play, pause, seek, mute) (see browser_docs). It is categorised as a Execute tool in the Browser MCP Server 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_control_media? +

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

What risk level is browser_control_media? +

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

Can I rate-limit browser_control_media? +

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

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

browser_control_media is provided by the Browser MCP Server MCP server (madebytokens/browser-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.