This record as markdown: /tools/hostinger-mcp/wp-memcached-status.md
What wp_memcached_status does on Hostinger
AI agents call wp_memcached_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_memcached_status is rated Low
This tool retrieves and displays the current state of a Memcached cache system. It performs no mutations, does not execute code, and produces no side effects—it is purely informational. The verb 'Show' confirms read-only behavior. Classification as Read with low severity is appropriate since cache status queries pose minimal security risk.
From the tool's definition Tool name 'wp_memcached_status' and description 'Show Memcached object cache status' indicate a query/inspection operation that retrieves status information without modifying or executing operations.
Attacks that exploit this kind of access
The rule that runs wp_memcached_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_memcached_status, this is the rule to start with:
wp_memcached_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_memcached_status call is checked against it from then on.
Questions about wp_memcached_status
Show Memcached object 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_memcached_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_memcached_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_memcached_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_memcached_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_memcached_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