scraping_status
Check if the Scrapling library is installed and available.
This record as markdown: /tools/cowork-os/scraping-status.md
What scraping_status does on CoWork OS
AI agents call scraping_status 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 scraping_status is rated Low
This tool performs a read-only query to determine library installation status. It retrieves information about the system environment without creating, modifying, deleting, or executing code. The operation has no side effects and poses minimal security risk even if misused by an agent.
From the tool's definition Tool name 'scraping_status' and description 'Check if the Scrapling library is installed and available' indicate a status check operation that queries system state without modification.
Attacks that exploit this kind of access
The rule that runs scraping_status 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 scraping_status, this is the rule to start with:
scraping_status 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 scraping_status call is checked against it from then on.
Questions about scraping_status
Check if the Scrapling library is installed and available. 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 scraping_status: 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.
scraping_status 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 scraping_status 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 scraping_status. 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.
scraping_status 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