Edit a generated WebZum site by describing the change in natural language. This is the primary editor tool. Given a user instruction (in conversationHistory), the WebZum editor builds the minimal site tree, sends it to an LLM with the user's verbatim words, applies the returned HTML diff across e...
Risk signalsAccepts raw HTML/template content (conversationHistory[].content)
Part of the WebZum - The Hosting Layer for AI-Generated Web Content server.
Free to start. No card required.
AI agents use update_site_html to create or modify resources in WebZum - The Hosting Layer for AI-Generated Web Content. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call update_site_html repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach WebZum - The Hosting Layer for AI-Generated Web Content.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"update_site_html": {
"limits": [
{
"counter": "update_site_html_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full WebZum - The Hosting Layer for AI-Generated Web Content policy for all 16 tools.
These attack patterns abuse exactly the kind of access update_site_html gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Edit a generated WebZum site by describing the change in natural language. This is the primary editor tool. Given a user instruction (in conversationHistory), the WebZum editor builds the minimal site tree, sends it to an LLM with the user's verbatim words, applies the returned HTML diff across every page that contains each affected section, and reassembles into a new version. Use this for nearly all edits: "make the hero say X", "remove the testimonials section", "change the about-us copy to be friendlier", "swap the order of the sections on the home page". Required: businessId, versionId, and a conversationHistory containing at least one user turn. The LLM reads the user's verbatim words — do not paraphrase. Returns { versionId, status: 'completed' | 'in_progress', ...extra }. If status is 'in_progress', the edit is still running in the background — poll get_site_status with the returned versionId every 5-10s until isComplete is true. Concurrency: edits on the same businessId MUST be serial. Never fire parallel edit calls on the same site; concurrent edits race and may return the wrong versionId. Wait for each edit to complete (status: 'completed' OR isComplete on get_site_status) before issuing the next one.. It is categorised as a Write tool in the WebZum - The Hosting Layer for AI-Generated Web Content MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the WebZum - The Hosting Layer for AI-Generated Web Content MCP server in PolicyLayer and add a rule for update_site_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 WebZum - The Hosting Layer for AI-Generated Web Content. Nothing to install.
update_site_html is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_site_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 update_site_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.
update_site_html is provided by the WebZum - The Hosting Layer for AI-Generated Web Content MCP server (https://webzum.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 16 WebZum - The Hosting Layer for AI-Generated Web Content tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.