dashboard_open · Lockstep MCP: Risk & Policy

WHAT IT DOES

What dashboard_open does on Lockstep

AI agents invoke dashboard_open to trigger actions in Lockstep. 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 dashboard_open needs a policy

This tool launches a browser to open a URL, which is an external operation/browser action rather than a simple read. It causes side effects in the environment (opening a browser window/process). Severity is medium since misuse would at most open unwanted browser windows but doesn't expose sensitive data or cause irreversible harm.

From the tool's definition 'Open the lockstep dashboard in a browser' — triggers an external browser action

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

dashboard_open Rate-limited

dashboard_open 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": {
    "dashboard_open": {
      "limits": [
        {
          "counter": "dashboard_open_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 Lockstep, so you can run agents against it safely.

FAQ

Questions about dashboard_open

What does the dashboard_open tool do? +

Open the lockstep dashboard in a browser. Call this to monitor progress visually. It is categorised as a Execute tool in the Lockstep MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on dashboard_open? +

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

What risk level is dashboard_open? +

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

Can I rate-limit dashboard_open? +

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

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

dashboard_open is provided by the Lockstep MCP server (tmmoore286/lockstep-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.