mouse_wheel · Playwright MCP Server MCP: Risk & Policy

WHAT IT DOES

What mouse_wheel does on Playwright MCP Server

AI agents invoke mouse_wheel to trigger actions in Playwright 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 mouse_wheel needs a policy

This tool executes a browser action (mouse wheel scroll) in a Playwright-controlled browser. It is an interactive browser operation that triggers UI events, placing it in the Execute category. The blast radius is low since scrolling alone does not modify data or cause destructive effects, but it can be used as part of a chain of actions to interact with web content.

From the tool's definition マウスホイールのスクロールを実行します — 'を実行します' means 'executes', indicating this triggers a browser interaction (mouse wheel scroll action)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mouse_wheel Rate-limited

mouse_wheel 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": {
    "mouse_wheel": {
      "limits": [
        {
          "counter": "mouse_wheel_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 Playwright MCP Server, so you can run agents against it safely.

FAQ

Questions about mouse_wheel

What does the mouse_wheel tool do? +

マウスホイールのスクロールを実行します. It is categorised as a Execute tool in the Playwright 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 mouse_wheel? +

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

What risk level is mouse_wheel? +

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

Can I rate-limit mouse_wheel? +

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

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

mouse_wheel is provided by the Playwright MCP Server MCP server (kotelberg/playwright-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.