This record as markdown: /tools/hostinger-mcp/wp-maintenance-toggle.md
What wp_maintenance_toggle does on Hostinger
AI agents invoke wp_maintenance_toggle 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_maintenance_toggle is rated High
Toggling maintenance mode triggers an external operational state change on a WordPress site — it makes the site inaccessible to visitors (on) or restores access (off). This is an operational action with real-world effects depending on arguments, fitting Execute. It is not purely a write of data, but rather activates/deactivates a system behavior. Misuse could cause site downtime, hence medium severity.
From the tool's definition Toggle maintenance mode on/off
Attacks that exploit this kind of access
The rule that runs wp_maintenance_toggle 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_maintenance_toggle, this is the rule to start with:
wp_maintenance_toggle 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_maintenance_toggle call is checked against it from then on.
Questions about wp_maintenance_toggle
Toggle maintenance mode on/off. 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_maintenance_toggle: 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_maintenance_toggle 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_maintenance_toggle 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_maintenance_toggle. 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_maintenance_toggle 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