Initialize a workflow with multiple isolated workers for parallel browser ops.
AI agents invoke workflow_init to trigger actions in OpenChrome. 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.
This tool spins up multiple isolated browser worker instances to execute parallel browser operations. Launching real browser automation workers is an Execute-class action — it triggers external processes whose effects depend on subsequent commands. The blast radius is high because initializing parallel lanes amplifies the scale of any downstream actions performed by those workers.
From the tool's definition Initialize a workflow with multiple isolated workers for parallel browser ops
Documented attack patterns abuse exactly the kind of access workflow_init gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OpenChrome, and nothing reaches the server without passing your rules. This is the rule we recommend for workflow_init:
{
"version": "1",
"default": "deny",
"tools": {
"workflow_init": {
"limits": [
{
"counter": "workflow_init_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}workflow_init 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.
Free to start. No card required.
Initialize a workflow with multiple isolated workers for parallel browser ops. It is categorised as a Execute tool in the OpenChrome MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the OpenChrome MCP server in PolicyLayer and add a rule for workflow_init: 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 OpenChrome. Nothing to install.
workflow_init is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the workflow_init 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.
Set action: deny in the PolicyLayer policy for workflow_init. 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.
workflow_init is provided by the OpenChrome MCP server (shaun0927/openchrome). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 106 OpenChrome tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
106 OpenChrome tools catalogued and risk-classified — across an index of 42,500+ MCP servers.