High Risk →

oc_session_resume

Restore working context after context compaction.

How to control oc_session_resume ↓

AI agents invoke oc_session_resume 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

Restoring a browser session reactivates an existing automation context, which constitutes triggering an external operation (browser state restoration). It doesn't purely read data — it re-establishes an active execution environment. Severity is medium because resuming a session could re-enable automated browser actions, though the tool itself may not directly cause harm.

From the tool's definition 'Restore working context after context compaction' — resumes a browser session/automation state

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

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

oc_session_resume 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_session_resume tool do? +

Restore working context after context compaction. 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_session_resume? +

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

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

Can I rate-limit oc_session_resume? +

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

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

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