[LEGACY] Scrape content from the current page. Use navigate_and_scrape instead.
AI agents call scrape_content 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.
Scraping content is a read operation that retrieves data from a page without side effects. No data is modified, deleted, or executed. The severity is low because even if an agent misuses this tool, the blast radius is limited to information disclosure from whatever page is in scope. The tool is marked as legacy and superseded by navigate_and_scrape, but the core capability remains a simple content retrieval function.
From the tool's definition Tool description explicitly states "Scrape content from the current page" with no mention of modification, deletion, or execution of code. The action is retrieval-only. The [LEGACY] tag indicates deprecation but does not change the fundamental operation.
Documented attack patterns abuse exactly the kind of access scrape_content 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_content:
{
"version": "1",
"default": "deny",
"tools": {
"scrape_content": {}
}
}scrape_content 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.
[LEGACY] Scrape content from the current page. Use navigate_and_scrape instead. 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 scrape_content: 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_content 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_content 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_content. 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_content 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.