browser_visualizer_stop

THE RISK

High Risk

Stopping a running HTTP service is an Execute action that triggers an external operation with side effects (terminating a process). While not destructive (the service can be restarted) or financial, it actively controls a system component.

From the tool's definition Stops the local Browser visualizer HTTP dashboard, which terminates a running service/process.

Documented attack patterns abuse exactly the kind of access browser_visualizer_stop gives an agent:

HOW TO CONTROL BROWSER_VISUALIZER_STOP

PolicyLayer is an MCP gateway — it sits between your AI agents and Godot Devtool, and nothing reaches the server without passing your rules. This is the rule we recommend for browser_visualizer_stop:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_visualizer_stop": {
      "limits": [
        {
          "counter": "browser_visualizer_stop_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

browser_visualizer_stop 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.

Create a free account and register Godot Devtool — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

More Godot Devtool tools

Destructive clear_debug_output Clear buffered output for the currently running Godot project Destructive delete_node Delete a non-root node from a Godot scene Destructive editor_delete_node Delete a non-root node from the currently open editor scene through UndoRedo Destructive filesystem_delete Delete a project-local file or directory with explicit confirmation Destructive filesystem_preview_delete Preview a project-local delete operation without deleting files Execute browser_visualizer_start Start a local read-only browser dashboard for Godot editor/runtime bridge status and live- Execute launch_editor Reuse an already connected Godot editor for a project, launch one only when no bridge is c Execute run_project Run the Godot project and capture output

All 101 Godot Devtool tools →

Execute tools on other servers

Frida Game Hacking MCP remove_breakpoint Procmon request_elevation WireMCP capture_packets Pentest Ai run_probe

Go deeper

High-risk tools in Godot Devtool → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the browser_visualizer_stop tool do? +

Stop the local Browser visualizer HTTP dashboard. It is categorised as a Execute tool in the Godot Devtool 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_visualizer_stop? +

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

What risk level is browser_visualizer_stop? +

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

Can I rate-limit browser_visualizer_stop? +

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

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

browser_visualizer_stop is provided by the Godot Devtool MCP server (wangdiandao/godot-devtool). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Godot Devtool tool call.

Deterministic rules across all 101 Godot Devtool tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

GOVERN GODOT DEVTOOL →

Free to start. No card required.

101 Godot Devtool tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// WHAT BROWSER_VISUALIZER_STOP ON GODOT DEVTOOL DOES

// THE RISK

// HOW TO CONTROL BROWSER_VISUALIZER_STOP

// EXPLORE