AI agents call scrape_webpage to retrieve information from FullScope-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Scraping webpages retrieves and queries data with no inherent side effects on the target system. While web scraping can raise policy concerns (rate limiting, ToS violations, potential unauthorized access), the tool itself performs read-only operations on remote content.
From the tool's definition Tool name and description indicate webpage content retrieval: 'scrape_webpage' and '抓取网页内容' (scrape webpage content). The optional file-saving capability ('可选保存为txt文件') is a secondary storage feature, not the primary function.
Documented attack patterns abuse exactly the kind of access scrape_webpage gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and FullScope-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for scrape_webpage:
{
"version": "1",
"default": "deny",
"tools": {
"scrape_webpage": {}
}
} scrape_webpage 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.
抓取网页内容,可选保存为txt文件. It is categorised as a Read tool in the FullScope-MCP MCP Server, which means it retrieves data without modifying state.
Register the FullScope- MCP server in PolicyLayer and add a rule for scrape_webpage: 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 FullScope-MCP. Nothing to install.
scrape_webpage 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_webpage 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_webpage. 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_webpage is provided by the FullScope- MCP server (yzfly/fullscope-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from FullScope-MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 FullScope-MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.