Shut down OpenChrome and close Chrome. Auto-relaunched on next tool call.
AI agents invoke oc_stop 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 a control operation that terminates a running process and closes a browser instance. While not destructive of data (the operation is reversible via auto-relaunch), it is an Execute action because it directly invokes external system operations whose outcomes depend on runtime conditions.
From the tool's definition Tool performs 'Shut down OpenChrome and close Chrome', which triggers an external operation (process termination) whose effects depend on system state and timing.
Documented attack patterns abuse exactly the kind of access oc_stop 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_stop:
{
"version": "1",
"default": "deny",
"tools": {
"oc_stop": {
"limits": [
{
"counter": "oc_stop_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}oc_stop 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.
Shut down OpenChrome and close Chrome. Auto-relaunched on next tool call. 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_stop: 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_stop 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_stop 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_stop. 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_stop 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.