This record as markdown: /tools/hostinger-mcp/wp-litespeed-status.md
What wp_litespeed_status does on Hostinger
AI agents call wp_litespeed_status to retrieve information from Hostinger without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why wp_litespeed_status is rated Low
This tool retrieves and displays the current state of LiteSpeed Cache configuration and status. It is a read-only query that has no side effects, does not modify data, execute code, or delete anything. The low severity reflects minimal blast radius even if misused by an AI agent—it would only expose cache status information.
From the tool's definition Tool name and description indicate a status query operation: 'Show LiteSpeed Cache status' is a retrieval action with no modification or execution of commands.
Attacks that exploit this kind of access
The rule that runs wp_litespeed_status 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_status, this is the rule to start with:
wp_litespeed_status is read-only, so it stays allowed. 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_status call is checked against it from then on.
Questions about wp_litespeed_status
Show LiteSpeed Cache status. It is categorised as a Read tool in the Hostinger MCP Server, which means it retrieves data without modifying state.
Register the Hostinger MCP server in PolicyLayer and add a rule for wp_litespeed_status: 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_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the wp_litespeed_status 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_status. 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_status 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.
This server
Across the catalogue