Block until the task reaches a terminal state (COMPLETED / FAILED /
AI agents invoke oc_task_wait 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 is Execute rather than Read because it's part of a Chrome automation control system where tasks are initiated by sibling tools (act, computer, drag_drop). Blocking on task completion and acting as a synchronization point means the tool manages the timing and sequencing of browser-based operations whose effects depend on what those upstream tasks do.
From the tool's definition Tool blocks execution "until the task reaches a terminal state"; controls Chrome browser automation where tasks can perform navigations, clicks, form submissions, or other browser actions.
Documented attack patterns abuse exactly the kind of access oc_task_wait 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_wait:
{
"version": "1",
"default": "deny",
"tools": {
"oc_task_wait": {
"limits": [
{
"counter": "oc_task_wait_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}oc_task_wait 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.
Block until the task reaches a terminal state (COMPLETED / FAILED /. 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_wait: 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_wait 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_wait 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_wait. 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_wait 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.