Low Risk

oc_reap_orphans

Manually sweep and terminate orphaned OpenChrome-managed Chrome processes. Never touches attach-mode or unmarked user Chrome.

How to control oc_reap_orphans ↓

AI agents call oc_reap_orphans to retrieve information from OpenChrome without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Even though oc_reap_orphans only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Documented attack patterns abuse exactly the kind of access oc_reap_orphans 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_reap_orphans:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "oc_reap_orphans": {}
  }
}

oc_reap_orphans is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register OpenChrome — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the oc_reap_orphans tool do? +

Manually sweep and terminate orphaned OpenChrome-managed Chrome processes. Never touches attach-mode or unmarked user Chrome. It is categorised as a Read tool in the OpenChrome MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on oc_reap_orphans? +

Register the OpenChrome MCP server in PolicyLayer and add a rule for oc_reap_orphans: 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.

What risk level is oc_reap_orphans? +

oc_reap_orphans is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit oc_reap_orphans? +

Yes. Add a rate_limit block to the oc_reap_orphans 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.

How do I block oc_reap_orphans completely? +

Set action: deny in the PolicyLayer policy for oc_reap_orphans. 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.

What MCP server provides oc_reap_orphans? +

oc_reap_orphans 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.

Enforce policy on every OpenChrome tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.