Execute a cached plan by ID, bypassing per-step LLM calls. Falls back gracefully on failure for manual retry.
AI agents invoke execute_plan 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 executes cached plans against a real browser without per-step LLM validation, creating significant blast radius if a malicious or incorrect plan is executed. It can trigger unintended browser actions, navigate to malicious sites, submit forms, or interact with web applications in harmful ways.
From the tool's definition Tool name 'execute_plan' and description 'Execute a cached plan' indicate execution of pre-compiled instructions.
Documented attack patterns abuse exactly the kind of access execute_plan 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 execute_plan:
{
"version": "1",
"default": "deny",
"tools": {
"execute_plan": {
"limits": [
{
"counter": "execute_plan_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}execute_plan 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.
Execute a cached plan by ID, bypassing per-step LLM calls. Falls back gracefully on failure for manual retry. 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 execute_plan: 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.
execute_plan 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 execute_plan 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 execute_plan. 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.
execute_plan 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.