ingest_html
Parse reference HTML into a structural blueprint (title, headings, paragraphs, images, buttons, colour palette) you can rebuild as BuilderX sections with new_section. Not a 1:1 clone.
This record as markdown: /tools/webcake-storefront/ingest-html.md
What ingest_html does on Webcake Storefront
AI agents call ingest_html to retrieve information from Webcake Storefront without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why ingest_html is rated Low
This tool retrieves and transforms information from HTML input into structured metadata (title, headings, paragraphs, images, buttons, colour palette). It has no side effects on the storefront, no data modification, and no irreversible actions. The misuse risk is minimal—an AI agent could only generate misleading structural blueprints, which would be caught downstream when actually applied to pages.
From the tool's definition Tool description states it "Parse[s] reference HTML into a structural blueprint" — it extracts and analyzes HTML structure without modifying, creating, or deleting any data.
Attacks that exploit this kind of access
The rule that runs ingest_html safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Webcake Storefront, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ingest_html, this is the rule to start with:
ingest_html is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Webcake Storefront, apply this rule, and every ingest_html call is checked against it from then on.
Questions about ingest_html
Parse reference HTML into a structural blueprint (title, headings, paragraphs, images, buttons, colour palette) you can rebuild as BuilderX sections with new_section. Not a 1:1 clone. It is categorised as a Read tool in the Webcake Storefront MCP Server, which means it retrieves data without modifying state.
Register the Webcake Storefront MCP server in PolicyLayer and add a rule for ingest_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 Webcake Storefront. Nothing to install.
ingest_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 ingest_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 ingest_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.
ingest_html is provided by the Webcake Storefront MCP server (webcake-storefront-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Webcake Storefront, and thousands of servers like it.
This server
Across the catalogue