browser_run_workflow · DevLab MCP Suite MCP: Risk & Policy

WHAT IT DOES

What browser_run_workflow does on DevLab MCP Suite

AI agents invoke browser_run_workflow to trigger actions in DevLab MCP Suite. 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 browser_run_workflow needs a policy

This tool runs predefined but external workflows on a browser, which qualifies as Execute rather than Read (it has side effects) or Write (effects are broader and less predictable than simple data modification). Severity is high due to the potential for workflows to perform unintended browser actions, manipulate content, or trigger uncontrolled automation sequences.

From the tool's definition Tool name 'browser_run_workflow' and description 'Execute a predefined workflow from a profile' indicates execution of arbitrary workflows.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_run_workflow Rate-limited

browser_run_workflow 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": {
    "browser_run_workflow": {
      "limits": [
        {
          "counter": "browser_run_workflow_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 DevLab MCP Suite, so you can run agents against it safely.

FAQ

Questions about browser_run_workflow

What does the browser_run_workflow tool do? +

Execute a predefined workflow from a profile (e.g., galaxy-raiders/smoke-menu). It is categorised as a Execute tool in the DevLab MCP Suite 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_run_workflow? +

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

What risk level is browser_run_workflow? +

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

Can I rate-limit browser_run_workflow? +

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

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

browser_run_workflow is provided by the DevLab MCP Suite MCP server (tanguito86/devlab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.