Get status of active and recent scraping jobs (worker runs automatically)
AI agents call get_scraping_status to retrieve information from ZMCPTools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves status information about existing scraping jobs. It performs a read-only query operation with no side effects, no code execution, and no data modification. The passive retrieval of job status information is the lowest-risk action in the security spectrum.
From the tool's definition Tool name 'get_scraping_status' and description 'Get status of active and recent scraping jobs' indicate a query/retrieval operation that returns status information without modifying or executing anything.
Documented attack patterns abuse exactly the kind of access get_scraping_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ZMCPTools, and nothing reaches the server without passing your rules. This is the rule we recommend for get_scraping_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_scraping_status": {}
}
}get_scraping_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get status of active and recent scraping jobs (worker runs automatically). It is categorised as a Read tool in the ZMCPTools MCP Server, which means it retrieves data without modifying state.
Register the ZMCPTools MCP server in PolicyLayer and add a rule for get_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 ZMCPTools. Nothing to install.
get_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 get_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 get_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.
get_scraping_status is provided by the ZMCPTools MCP server (zachhandley/zmcptools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 70 ZMCPTools tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
70 ZMCPTools tools catalogued and risk-classified — across an index of 42,500+ MCP servers.