Scrape documentation from a website using intelligent sub-agents. Jobs are queued and processed automatically by the background worker. Supports plain string selectors for content extraction.
AI agents invoke scrape_documentation to trigger actions in ZMCPTools. 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.
This tool triggers external operations (web scraping via sub-agents, background worker job queuing) that interact with remote websites. It is not a simple read/fetch — it spawns agents, queues jobs, and processes them automatically, making it an Execute-category action. Misuse could result in unintended scraping of unauthorized sites or resource exhaustion, warranting medium severity.
From the tool's definition 'Scrape documentation from a website using intelligent sub-agents. Jobs are queued and processed automatically by the background worker.'
Documented attack patterns abuse exactly the kind of access scrape_documentation 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 scrape_documentation:
{
"version": "1",
"default": "deny",
"tools": {
"scrape_documentation": {
"limits": [
{
"counter": "scrape_documentation_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}scrape_documentation 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.
Free to start. No card required.
Scrape documentation from a website using intelligent sub-agents. Jobs are queued and processed automatically by the background worker. Supports plain string selectors for content extraction. It is categorised as a Execute tool in the ZMCPTools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ZMCPTools MCP server in PolicyLayer and add a rule for scrape_documentation: 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.
scrape_documentation is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the scrape_documentation 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_documentation. 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_documentation 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.