hosting_clearWebsiteCacheV1
Permanently clears all server-side cache for the website at once. Use it when content was updated and needs to be visible immediately, or after making major changes. Also purges the Hostinger CDN cache when CDN is enabled on the website. For a WordPress installation living in a subdirectory, pass...
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/hosting-clearwebsitecachev1.md
What hosting_clearWebsiteCacheV1 does on Hostinger Api
AI agents call hosting_clearWebsiteCacheV1 to permanently remove resources in Hostinger Api, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
domain | string | Yes | Domain name |
username | string | Yes | username parameter |
directory | string | — | Directory of the website installation to clear, relative to the website root. Defaults to the website root. |
Parameters from the server's own tool schema.
Why hosting_clearWebsiteCacheV1 is rated Critical
The word 'permanently' and 'at once' indicate this is an irreversible bulk operation — once cache is cleared, the cached data cannot be restored. While clearing cache is generally a low-impact operation (the cache will rebuild), it is irreversible in the sense that the cached data is gone and cannot be undone. It also affects CDN cache across the board.
From the tool's definition Permanently clears all server-side cache for the website at once
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs hosting_clearWebsiteCacheV1 safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hostinger Api, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hosting_clearWebsiteCacheV1, this is the rule to start with:
hosting_clearWebsiteCacheV1 is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger Api, apply this rule, and every hosting_clearWebsiteCacheV1 call is checked against it from then on.
Questions about hosting_clearWebsiteCacheV1
Permanently clears all server-side cache for the website at once. Use it when content was updated and needs to be visible immediately, or after making major changes. Also purges the Hostinger CDN cache when CDN is enabled on the website. For a WordPress installation living in a subdirectory, pass the directory query parameter to clear its cache. It is categorised as a Destructive tool in the Hostinger Api MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
hosting_clearWebsiteCacheV1 accepts 3 parameters: domain, username, directory. Required: domain, username. The full parameter table on this page comes from the server's own tool schema.
Register the Hostinger Api MCP server in PolicyLayer and add a rule for hosting_clearWebsiteCacheV1: 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 Hostinger Api. Nothing to install.
hosting_clearWebsiteCacheV1 is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the hosting_clearWebsiteCacheV1 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 hosting_clearWebsiteCacheV1. 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.
hosting_clearWebsiteCacheV1 is provided by the Hostinger Api MCP server (hostinger-api-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hostinger Api, and thousands of servers like it.
Across the catalogue