Start an opt-in goal-level TaskRun. Tracks user goal, success criteria, progress summary, item progress, and evidence across multiple OpenChrome tool calls without changing existing browser tools.
AI agents invoke oc_task_run_start 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.
While the tool itself does not directly perform destructive, financial, or write operations, it triggers and coordinates execution of other browser automation tools based on user-provided goals and success criteria. This is an Execute tool because it initiates automated workflows whose effects depend on the goal arguments and which orchestrated actions the user requests.
From the tool's definition Tool description states it 'Start[s] an opt-in goal-level TaskRun' and 'Tracks user goal, success criteria, progress summary, item progress, and evidence across multiple OpenChrome tool calls.' The term 'TaskRun' combined with tracking across 'multiple' tool…
Documented attack patterns abuse exactly the kind of access oc_task_run_start 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 oc_task_run_start:
{
"version": "1",
"default": "deny",
"tools": {
"oc_task_run_start": {
"limits": [
{
"counter": "oc_task_run_start_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}oc_task_run_start 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.
Start an opt-in goal-level TaskRun. Tracks user goal, success criteria, progress summary, item progress, and evidence across multiple OpenChrome tool calls without changing existing browser tools. 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 oc_task_run_start: 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.
oc_task_run_start 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 oc_task_run_start 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 oc_task_run_start. 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.
oc_task_run_start 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.