browser_check_checkbox · Playwright MCP Server MCP

WHAT IT DOES

What browser_check_checkbox does on Playwright MCP Server

AI agents invoke browser_check_checkbox 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 browser_check_checkbox needs a policy

Checking a checkbox is a browser automation action that modifies the state of a UI element. While it may seem minor, in the context of a browser automation server it constitutes an Execute-level action since it interacts with external web pages and can trigger downstream effects (e.g., enabling options, submitting forms, changing settings). It is more severe than a pure Read but less severe than destructive actions.

From the tool's definition 'Check a checkbox' — triggers a browser interaction (clicking/checking a UI element) which constitutes a browser action with potential side effects depending on the form/page context

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_check_checkbox Rate-limited

browser_check_checkbox 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_check_checkbox": {
      "limits": [
        {
          "counter": "browser_check_checkbox_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 browser_check_checkbox

What does the browser_check_checkbox tool do? +

Check a checkbox. 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 browser_check_checkbox? +

Register the Playwright MCP Server MCP server in PolicyLayer and add a rule for browser_check_checkbox: 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 browser_check_checkbox? +

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

Can I rate-limit browser_check_checkbox? +

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

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

browser_check_checkbox is provided by the Playwright MCP Server MCP server (nolecram/build_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.