stop_dashboard · Claude Team MCP: Risk & Policy

WHAT IT DOES

What stop_dashboard does on Claude Team MCP

AI agents invoke stop_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 stop_dashboard needs a policy

This tool executes a control command to halt a dashboard service. While stopping a dashboard is typically reversible (it can be restarted), the action itself is an external operation triggered by an agent with effects that depend on the current state of the system. This fits Execute rather than Write because it is commanding an external system state change (process termination) rather than modifying persistent data.

From the tool's definition Tool name and description indicate it 'Stop[s] the live web dashboard if it's running' — an action that terminates a running process or service.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_dashboard Rate-limited

stop_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": {
    "stop_dashboard": {
      "limits": [
        {
          "counter": "stop_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 stop_dashboard

What does the stop_dashboard tool do? +

Stop the live web dashboard if it's running. 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 stop_dashboard? +

Register the Claude Team MCP server in PolicyLayer and add a rule for stop_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 stop_dashboard? +

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

Can I rate-limit stop_dashboard? +

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

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

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