Fetch a web page and return its main readable content as clean Markdown.
AI agents call scrape_url to retrieve information from ToolCenter MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves public web content and transforms it into a readable format. It performs no writes, executions, destructive actions, or financial operations. The primary risk is minimal — standard web scraping with no side effects on the target system beyond normal HTTP requests. Confidence is high because the description is explicit about read-only behavior.
From the tool's definition Tool description states 'Fetch a web page and return its main readable content' — this is data retrieval with no modification or side effects. The verb 'scrape' combined with 'fetch' and 'return' confirms it reads and extracts existing content.
Attacks that exploit this kind of access
Fetch a web page and return its main readable content as clean Markdown. It is categorised as a Read tool in the ToolCenter MCP MCP Server, which means it retrieves data without modifying state.
Register the ToolCenter MCP server in PolicyLayer and add a rule for scrape_url: 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 ToolCenter MCP. Nothing to install.
scrape_url 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_url 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_url. 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_url is provided by the ToolCenter MCP server (toolcenter-dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →