New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

wp_litespeed_status

Show LiteSpeed Cache status.

SERVERHostinger SOURCEidugeni/hostinger-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about wp_litespeed_status

What does the wp_litespeed_status tool do? +

Show LiteSpeed Cache status. It is categorised as a Read tool in the Hostinger MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on wp_litespeed_status? +

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.

What risk level is wp_litespeed_status? +

wp_litespeed_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit wp_litespeed_status? +

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.

How do I block wp_litespeed_status completely? +

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.

What MCP server provides wp_litespeed_status? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Hostinger's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.