[STATELESS] Get sanitized/processed HTML for inspection and automation planning. Use when: finding form fields/selectors, analyzing page structure before automation, building schemas. Returns cleaned HTML showing element names, IDs, and classes - perfect for identifying selectors for subsequent c...
AI agents call get_html to retrieve information from MCP Server for Crawl4AI without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and processes web content for analysis without causing side effects. It reads HTML structure and returns sanitized output for inspection and planning purposes. While it supports automation planning, the tool itself only extracts and returns data—it does not execute automation, modify content, or interact with external systems.
From the tool's definition Tool description states it is '[STATELESS]' and is used for 'inspection', 'analyzing page structure', 'finding form fields/selectors', and 'identifying selectors'. It 'Returns cleaned HTML' for analysis purposes.
Documented attack patterns abuse exactly the kind of access get_html gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Server for Crawl4AI, and nothing reaches the server without passing your rules. This is the rule we recommend for get_html:
{
"version": "1",
"default": "deny",
"tools": {
"get_html": {}
}
}get_html 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.
[STATELESS] Get sanitized/processed HTML for inspection and automation planning. Use when: finding form fields/selectors, analyzing page structure before automation, building schemas. Returns cleaned HTML showing element names, IDs, and classes - perfect for identifying selectors for subsequent crawl operations. Commonly used before crawl to find selectors for automation. Creates new browser each time. It is categorised as a Read tool in the MCP Server for Crawl4AI MCP Server, which means it retrieves data without modifying state.
Register the MCP Server for Crawl4AI MCP server in PolicyLayer and add a rule for get_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 MCP Server for Crawl4AI. Nothing to install.
get_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 get_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 get_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.
get_html is provided by the MCP Server for Crawl4AI MCP server (omgwtfwow/mcp-crawl4ai-ts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Server for Crawl4AI, 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.
10 MCP Server for Crawl4AI tools catalogued and risk-classified — across an index of 43,000+ MCP servers.