start_dashboard · Claude Team MCP: Risk & Policy

WHAT IT DOES

What start_dashboard does on Claude Team MCP

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

Starting a dashboard constitutes executing an external operation that initiates services and processes. While not destructive or financial, it goes beyond read/write data operations—it actively triggers and controls running processes. The incomplete description limits confidence slightly, but the verb 'Launch' and 'live web dashboard' clearly indicate process execution.

From the tool's definition Tool 'start_dashboard' launches ('Launch') a live web dashboard, which triggers external operations (web server startup, network binding) whose effects depend on runtime arguments and system state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_dashboard Rate-limited

start_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": {
    "start_dashboard": {
      "limits": [
        {
          "counter": "start_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 Team MCP, so you can run agents against it safely.

FAQ

Questions about start_dashboard

What does the start_dashboard tool do? +

Launch a live web dashboard showing the board, channel, agents, debate, and. It is categorised as a Execute tool in the Claude Team MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on start_dashboard? +

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

What risk level is start_dashboard? +

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

Can I rate-limit start_dashboard? +

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

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

start_dashboard is provided by the Claude Team MCP server (lakshan12367/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.