media_record_video

THE RISK

High Risk

Why media_record_video needs a policy

While video recording itself is not destructive or financial, it is an Execute operation because it triggers and controls an external process (browser video recording) whose side effects are contingent on user-supplied arguments. The medium severity reflects that misuse could capture sensitive screen content or exhaust system resources, but the impact is limited compared to code execution or data deletion.

From the tool's definition Tool enables 'Video recording control' with start/stop actions on a real Chromium browser. This initiates and controls external browser operations whose effects (recording state, file generation, resource consumption) depend on the action argument.

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

POLICY

How to control media_record_video

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

policy.json

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

media_record_video 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 Browser-Debugger — 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 Browser-Debugger tools

Destructive browser_close Closes browser and saves all artifacts (video, logs, screenshots, HAR, trace). Execute browser_launch 🔴 ALWAYS USE THIS FIRST - Starts browser automation. Execute app_interact Universal form filler and button clicker. fields: list of values, button: button text hint Execute viewport_set_mode Changes viewport. mode: 'iphone', 'ipad', or 'desktop'. Read performance_get_metrics Analyzes page performance (Core Web Vitals: LCP, FCP, CLS). Read debug_read_logs Reads console and network logs (last 20 each). Read dom_get_source Returns HTML source of current page (truncated to 5000 chars). Read dom_inspect_element Inspects element visibility, position, and attributes. Use selector OR xpath.

All 14 Browser-Debugger 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 Browser-Debugger → 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 media_record_video

What does the media_record_video tool do? +

Video recording control. action: 'start' or 'stop'. It is categorised as a Execute tool in the Browser-Debugger MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on media_record_video? +

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

What risk level is media_record_video? +

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

Can I rate-limit media_record_video? +

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

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

media_record_video is provided by the Browser-Debugger MCP server (selvadinesh-giga/mcp-based-browser-debug-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Browser-Debugger tool call.

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

CHECK YOUR STACK →