Finish an opt-in OpenChrome run ledger with a terminal, needs_user_input, or needs_strategy_change status.
AI agents use oc_run_finish to create or update resources in OpenChrome — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OpenChrome environment.
This tool updates the state/status of a run ledger record, which is a write operation (modifying run metadata to a terminal or other status). It does not execute code, delete data irreversibly, or involve financial transactions. The severity is medium because it affects the state of an ongoing automation run, potentially halting or redirecting automated browser sessions.
From the tool's definition Finish an opt-in OpenChrome run ledger with a terminal, needs_user_input, or needs_strategy_change status
Documented attack patterns abuse exactly the kind of access oc_run_finish 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_run_finish:
{
"version": "1",
"default": "deny",
"tools": {
"oc_run_finish": {
"limits": [
{
"counter": "oc_run_finish_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}oc_run_finish stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Finish an opt-in OpenChrome run ledger with a terminal, needs_user_input, or needs_strategy_change status. It is categorised as a Write tool in the OpenChrome MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the OpenChrome MCP server in PolicyLayer and add a rule for oc_run_finish: 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_run_finish is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the oc_run_finish 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_run_finish. 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_run_finish 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.