agency_cache_clear
Clear cache for an Agency Plan website.
This record as markdown: /tools/hostinger-mcp/agency-cache-clear.md
What agency_cache_clear does on Hostinger
AI agents call agency_cache_clear to permanently remove resources in Hostinger, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why agency_cache_clear is rated Critical
Clearing a cache is a non-reversible action: the cached data is destroyed and cannot be recovered (only rebuilt by re-caching). While the blast radius is limited (no permanent business data is lost, just cached content that can be regenerated), it still qualifies as Destructive due to its irreversible nature.
From the tool's definition 'Clear cache' — irreversibly removes cached data for a website
Attacks that exploit this kind of access
The rule that runs agency_cache_clear safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hostinger, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For agency_cache_clear, this is the rule to start with:
agency_cache_clear 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, apply this rule, and every agency_cache_clear call is checked against it from then on.
Questions about agency_cache_clear
Clear cache for an Agency Plan website. It is categorised as a Destructive tool in the Hostinger MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Hostinger MCP server in PolicyLayer and add a rule for agency_cache_clear: 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. Nothing to install.
agency_cache_clear 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 agency_cache_clear 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 agency_cache_clear. 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.
agency_cache_clear is provided by the Hostinger MCP server (idugeni/hostinger-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hostinger, and thousands of servers like it.
Across the catalogue