This record as markdown: /tools/hostinger-mcp/wp-litespeed-purge.md
What wp_litespeed_purge does on Hostinger
AI agents invoke wp_litespeed_purge to trigger actions in Hostinger. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why wp_litespeed_purge is rated High
Cache purging is not a simple read, nor does it permanently delete user/business data (making it non-Destructive in the critical sense), but it executes an external operation on the web server's caching layer. Misuse could cause performance degradation by forcing cache rebuilds under load, but it is recoverable. Classified as Execute due to triggering an external system operation with side effects.
From the tool's definition "Purge the LiteSpeed Cache" — purging a cache is an operational action that clears cached data and triggers cache rebuilding, affecting site performance and behavior.
Attacks that exploit this kind of access
The rule that runs wp_litespeed_purge 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 wp_litespeed_purge, this is the rule to start with:
wp_litespeed_purge stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger, apply this rule, and every wp_litespeed_purge call is checked against it from then on.
Questions about wp_litespeed_purge
Purge the LiteSpeed Cache. It is categorised as a Execute tool in the Hostinger MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Hostinger MCP server in PolicyLayer and add a rule for wp_litespeed_purge: 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.
wp_litespeed_purge is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the wp_litespeed_purge 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 wp_litespeed_purge. 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.
wp_litespeed_purge 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