High Risk →

oc_proxy_hook

Pilot-tier (--pilot + OPENCHROME_PROXY_HOOK=1): bind host-supplied

How to control oc_proxy_hook ↓

AI agents invoke oc_proxy_hook 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.

High Risk

The tool appears to bind host-supplied proxy hooks in a live browser automation environment, which constitutes executing an external operation with potentially broad network-level side effects. The description is severely truncated, lowering confidence, but the pattern of 'hook' + 'bind' in a browser automation context most closely maps to Execute.

From the tool's definition 'bind host-supplied' — description is truncated/uninformative, but the name 'proxy_hook' combined with the server context (real Chrome browser automation) and 'Pilot-tier' flag suggests it binds/intercepts network proxy hooks, triggering external operations

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "oc_proxy_hook": {
      "limits": [
        {
          "counter": "oc_proxy_hook_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  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.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the oc_proxy_hook tool do? +

Pilot-tier (--pilot + OPENCHROME_PROXY_HOOK=1): bind host-supplied. 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.

How do I enforce a policy on oc_proxy_hook? +

Register the OpenChrome MCP server in PolicyLayer and add a rule for oc_proxy_hook: 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_proxy_hook? +

oc_proxy_hook is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit oc_proxy_hook? +

Yes. Add a rate_limit block to the oc_proxy_hook 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_proxy_hook completely? +

Set action: deny in the PolicyLayer policy for oc_proxy_hook. 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_proxy_hook? +

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