wp_check_valid
Check if WordPress installations are valid/intact.
This record as markdown: /tools/hostinger-mcp/wp-check-valid.md
What wp_check_valid does on Hostinger
AI agents call wp_check_valid 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_check_valid is rated Low
This tool performs a check or validation of WordPress installations to determine their integrity status. It retrieves information about whether installations are valid/intact but does not modify, execute code, delete, or move money. This is a read-only diagnostic operation with minimal risk if misused by an AI agent.
From the tool's definition Tool name 'wp_check_valid' and description 'Check if WordPress installations are valid/intact' indicate a validation/diagnostic operation that queries state without modification or execution.
Attacks that exploit this kind of access
The rule that runs wp_check_valid 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_check_valid, this is the rule to start with:
wp_check_valid 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_check_valid call is checked against it from then on.
Questions about wp_check_valid
Check if WordPress installations are valid/intact. 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_check_valid: 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_check_valid 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_check_valid 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_check_valid. 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_check_valid 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