execute_webmcp_tool

Executes a WebMCP tool exposed by the page.

SERVERChrome Devtools SOURCE@async23/chrome-devtools-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/async23-chrome-devtools-mcp/execute-webmcp-tool.md

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.

RISK

Why execute_webmcp_tool is rated High

This tool runs external code/operations (WebMCP tools) whose effects are determined by the arguments passed and the tools exposed by the page. It has no built-in safeguards against misuse and could trigger unintended side effects, data exfiltration, or malicious actions depending on what tools are available on the page.

From the tool's definition Tool description states it 'Executes a WebMCP tool exposed by the page' — the verb 'executes' combined with arbitrary tool invocation on a live browser indicates code/command execution capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs execute_webmcp_tool safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Chrome Devtools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For execute_webmcp_tool, this is the rule to start with:

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.

The button opens the PolicyLayer dashboard: create your workspace, connect Chrome Devtools, apply this rule, and every execute_webmcp_tool call is checked against it from then on.

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 (@async23/chrome-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Chrome Devtools, and thousands of servers like it.

This server

All 50 Chrome Devtools tools → High-risk tools on this server →

Across the catalogue

claude_execute on Claude Bridge →execute_test_case on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →