scrape_session

Run a multi-step scraping session with persistent browser state.

SERVERCoWork OS SOURCECoWork-OS/CoWork-OS

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cowork-os/scrape-session.md

WHAT IT DOES

What scrape_session does on CoWork OS

AI agents invoke scrape_session to trigger actions in CoWork OS. 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.

RISK

Why scrape_session is rated High

The tool triggers external operations (web scraping) via a browser with maintained state across multiple steps. This is an Execute category because it runs code/commands whose side effects are contingent on how an agent configures the scraping session.

From the tool's definition "Run a multi-step scraping session with persistent browser state" — this tool executes browser actions and operations whose effects depend on arguments (the scraping targets and steps defined).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs scrape_session safely

PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For scrape_session, this is the rule to start with:

scrape_session Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "scrape_session": {
      "limits": [
        {
          "counter": "scrape_session_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect CoWork OS, apply this rule, and every scrape_session call is checked against it from then on.

FAQ

Questions about scrape_session

What does the scrape_session tool do? +

Run a multi-step scraping session with persistent browser state. It is categorised as a Execute tool in the CoWork OS MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on scrape_session? +

Register the CoWork OS MCP server in PolicyLayer and add a rule for scrape_session: 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 CoWork OS. Nothing to install.

What risk level is scrape_session? +

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

Can I rate-limit scrape_session? +

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

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

scrape_session is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CoWork OS, and thousands of servers like it.

This server

All 342 CoWork OS tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →