open_dashboard · Claude Viewer MCP: Risk & Policy

WHAT IT DOES

What open_dashboard does on Claude Viewer

AI agents invoke open_dashboard to trigger actions in Claude Viewer. 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 open_dashboard needs a policy

This tool starts a web server process and triggers a browser action (opening a URL), both of which are external operations with side effects. Starting a server binds a port and runs a background process; opening a browser is an OS-level action. Neither is a simple read, write, or destructive operation — it executes system-level operations whose effects depend on the environment.

From the tool's definition 'Start the Claude Viewer web server and open the dashboard in your default browser'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

open_dashboard Rate-limited

open_dashboard 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": {
    "open_dashboard": {
      "limits": [
        {
          "counter": "open_dashboard_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 Claude Viewer, so you can run agents against it safely.

FAQ

Questions about open_dashboard

What does the open_dashboard tool do? +

Start the Claude Viewer web server and open the dashboard in your default browser. It is categorised as a Execute tool in the Claude Viewer MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on open_dashboard? +

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

What risk level is open_dashboard? +

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

Can I rate-limit open_dashboard? +

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

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

open_dashboard is provided by the Claude Viewer MCP server (maxturazzini/claude-viewer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.