Update an existing published website with new HTML content. Requires authentication via edit_key (from the original publish response) or api_key (from the user's dashboard after claiming the site). The html field replaces the entire page — this is a full replacement, not a patch. You can also upd...
Risk signalsAccepts raw HTML/template content (html) · Handles credentials or secrets (api_key) · Bulk/mass operation — affects multiple targets
Part of the YeetIt server.
Free to start. No card required.
AI agents use update_website to create or modify resources in YeetIt. 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_website 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 YeetIt.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"update_website": {
"limits": [
{
"counter": "update_website_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full YeetIt policy for all 4 tools.
These attack patterns abuse exactly the kind of access update_website 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.
Update an existing published website with new HTML content. Requires authentication via edit_key (from the original publish response) or api_key (from the user's dashboard after claiming the site). The html field replaces the entire page — this is a full replacement, not a patch. You can also update assets. Use this when a user asks you to modify, edit, or change a site you previously published. IMPORTANT: You must provide either edit_key or api_key for authentication.. It is categorised as a Write tool in the YeetIt MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the YeetIt MCP server in PolicyLayer and add a rule for update_website: 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 YeetIt. Nothing to install.
update_website 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_website 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_website. 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_website is provided by the YeetIt MCP server (https://yeetit.site/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 YeetIt 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.