hosting_setAIOptionStatusV1

SERVERHostinger Api SOURCEhostinger-api-mcp

Medium RISK CLASS

Category Write

Parameters 44 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/hosting-setaioptionstatusv1.md

WHAT IT DOES

What hosting_setAIOptionStatusV1 does on Hostinger Api

AI agents use hosting_setAIOptionStatusV1 to create or update resources in Hostinger Api, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hostinger Api environment.

Parameter	Type	Required	Description
`enable`	boolean	Yes	Enable (true) or disable (false) the AI option.
`option`	string	Yes	AI option name
`software`	string	Yes	WordPress installation (software) identifier
`username`	string	Yes	username parameter

Parameters from the server's own tool schema.

RISK

Why hosting_setAIOptionStatusV1 is rated Medium

This tool creates or modifies data (WordPress plugin AI option settings) in a reversible manner. While it affects a live WordPress installation, the modification is a configuration toggle that can be undone, making it Write rather than Execute or Destructive.

From the tool's definition Tool description explicitly states 'Enable or disable an AI option' which modifies configuration state on a specified WordPress installation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs hosting_setAIOptionStatusV1 safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Hostinger Api, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hosting_setAIOptionStatusV1, this is the rule to start with:

hosting_setAIOptionStatusV1 Rate-limited

hosting_setAIOptionStatusV1 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "hosting_setAIOptionStatusV1": {
      "limits": [
        {
          "counter": "hosting_setaioptionstatusv1_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger Api, apply this rule, and every hosting_setAIOptionStatusV1 call is checked against it from then on.

FAQ

Questions about hosting_setAIOptionStatusV1

What does the hosting_setAIOptionStatusV1 tool do? +

Enable or disable an AI option for the Hostinger Tools plugin on the specified WordPress installation. Provide the WordPress installation (software) identifier in the path. It can be obtained from GET /api/hosting/v1/wordpress/installations (the id field). It is categorised as a Write tool in the Hostinger Api MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does hosting_setAIOptionStatusV1 accept? +

hosting_setAIOptionStatusV1 accepts 4 parameters: enable, option, software, username. Required: enable, option, software, username. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on hosting_setAIOptionStatusV1? +

Register the Hostinger Api MCP server in PolicyLayer and add a rule for hosting_setAIOptionStatusV1: 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 Api. Nothing to install.

What risk level is hosting_setAIOptionStatusV1? +

hosting_setAIOptionStatusV1 is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit hosting_setAIOptionStatusV1? +

Yes. Add a rate_limit block to the hosting_setAIOptionStatusV1 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 hosting_setAIOptionStatusV1 completely? +

Set action: deny in the PolicyLayer policy for hosting_setAIOptionStatusV1. 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 hosting_setAIOptionStatusV1? +

hosting_setAIOptionStatusV1 is provided by the Hostinger Api MCP server (hostinger-api-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Hostinger Api, and thousands of servers like it.

This server

All 258 Hostinger Api tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →