This record as markdown: /tools/hostinger-mcp/wp-themes-activate.md
What wp_themes_activate does on Hostinger
AI agents use wp_themes_activate to create or update resources in Hostinger, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hostinger environment.
Why wp_themes_activate is rated Medium
This operation modifies site state by changing which theme is active. It is reversible (another theme can be activated instead) and not destructive or financial. While it could affect site appearance/functionality if a problematic theme is activated, it does not execute arbitrary code, delete data, or move money. The primary intent is data/state modification rather than execution of arbitrary operations or code.
From the tool's definition The tool name 'wp_themes_activate' and description 'Activate a WordPress theme' indicate a modification to WordPress site configuration. Activating a theme changes the active theme setting, which is a reversible configuration change.
Attacks that exploit this kind of access
The rule that runs wp_themes_activate 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_themes_activate, this is the rule to start with:
wp_themes_activate stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_themes_activate call is checked against it from then on.
Questions about wp_themes_activate
Activate a WordPress theme. It is categorised as a Write tool in the Hostinger MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Hostinger MCP server in PolicyLayer and add a rule for wp_themes_activate: 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_themes_activate is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the wp_themes_activate 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_themes_activate. 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_themes_activate 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