webtool_debug · Webtools MCP Server MCP: Risk & Policy

WHAT IT DOES

What webtool_debug does on Webtools MCP Server

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

This tool actively runs a browser session against a target webpage, executes JavaScript to capture console output, intercepts network requests, and performs device emulation. These are active browser operations with external side effects depending on the URL/arguments provided, placing it firmly in the Execute category.

From the tool's definition 'Debug a webpage by capturing console output, network requests, errors, and layout thrashing with custom device emulation'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

webtool_debug Rate-limited

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

FAQ

Questions about webtool_debug

What does the webtool_debug tool do? +

Debug a webpage by capturing console output, network requests, errors, and layout thrashing with custom device emulation. Includes advanced response size management with pagination, output limits, and compact formatting to stay within MCP token limits. It is categorised as a Execute tool in the Webtools 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 webtool_debug? +

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

What risk level is webtool_debug? +

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

Can I rate-limit webtool_debug? +

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

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

webtool_debug is provided by the Webtools MCP Server MCP server (misterboe/webtools-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.