scrape_multiple
Scrape multiple URLs in a single operation. Efficient for batch extraction
This record as markdown: /tools/cowork-os/scrape-multiple.md
What scrape_multiple does on CoWork OS
AI agents call scrape_multiple to retrieve information from CoWork OS without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why scrape_multiple is rated Low
The tool fetches and extracts content from multiple web URLs — a read/retrieval operation with no explicit write or destructive side effects. Severity is medium because batch scraping can exfiltrate large amounts of data at scale, hit rate limits, or access sensitive pages, but it does not modify or delete any data.
From the tool's definition 'Scrape multiple URLs in a single operation. Efficient for batch extraction'
Attacks that exploit this kind of access
The rule that runs scrape_multiple 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_multiple, this is the rule to start with:
scrape_multiple is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect CoWork OS, apply this rule, and every scrape_multiple call is checked against it from then on.
Questions about scrape_multiple
Scrape multiple URLs in a single operation. Efficient for batch extraction. It is categorised as a Read tool in the CoWork OS MCP Server, which means it retrieves data without modifying state.
Register the CoWork OS MCP server in PolicyLayer and add a rule for scrape_multiple: 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.
scrape_multiple is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the scrape_multiple 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 scrape_multiple. 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.
scrape_multiple 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.
More on CoWork OS, and thousands of servers like it.
This server
Across the catalogue