execute_webmcp_tool · Chrome Devtools MCP: Risk & Policy

WHAT IT DOES

What execute_webmcp_tool does on Chrome Devtools

AI agents invoke execute_webmcp_tool to trigger actions in Chrome Devtools. 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 execute_webmcp_tool needs a policy

This tool allows running external code or operations exposed by a webpage without predictable boundaries. The effects depend entirely on what tools the page exposes, making this Execute rather than Write or Read. Severity is high because uncontrolled execution of page-exposed tools could exfiltrate data, modify page state, trigger external APIs, or cause unexpected side effects.

From the tool's definition Tool name 'execute_webmcp_tool' and description 'Executes a WebMCP tool exposed by the page' indicate execution of arbitrary tools/code provided by the webpage.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_webmcp_tool Rate-limited

execute_webmcp_tool 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": {
    "execute_webmcp_tool": {
      "limits": [
        {
          "counter": "execute_webmcp_tool_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 Chrome Devtools, so you can run agents against it safely.

FAQ

Questions about execute_webmcp_tool

What does the execute_webmcp_tool tool do? +

Executes a WebMCP tool exposed by the page. It is categorised as a Execute tool in the Chrome Devtools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on execute_webmcp_tool? +

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

What risk level is execute_webmcp_tool? +

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

Can I rate-limit execute_webmcp_tool? +

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

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

execute_webmcp_tool is provided by the Chrome Devtools MCP server (shivamprasad99/chrome-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.