Extract preprocessed HTML from a webpage.
AI agents call extract_html to retrieve information from Crawl4AI MCP Wrapper without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns HTML content from a webpage. It performs a read-only operation with no capability to modify, delete, or execute code. The verb 'extract' combined with 'preprocessed HTML' confirms data retrieval. While the Crawl4AI server supports JavaScript execution and other capabilities, this specific tool is limited to content extraction, making it a Read operation with low severity.
From the tool's definition Tool name 'extract_html' and description 'Extract preprocessed HTML from a webpage' indicates retrieval of data with no modification or side effects.
Attacks that exploit this kind of access
Extract preprocessed HTML from a webpage. It is categorised as a Read tool in the Crawl4AI MCP Wrapper MCP Server, which means it retrieves data without modifying state.
Register the Crawl4AI MCP Wrapper MCP server in PolicyLayer and add a rule for extract_html: 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 Crawl4AI MCP Wrapper. Nothing to install.
extract_html 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 extract_html 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 extract_html. 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.
extract_html is provided by the Crawl4AI MCP Wrapper MCP server (joedank/mcpcrawl4ai). 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 →