hosting_createWebsiteSubdomainV1

Create a new subdomain for the selected website. Provide a subdomain prefix and, optionally, a custom directory or the website public directory to use as the subdomain root.

SERVERHostinger Api SOURCEhostinger-api-mcp

Medium RISK CLASS

Category Write

Parameters 53 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-createwebsitesubdomainv1.md

WHAT IT DOES

What hosting_createWebsiteSubdomainV1 does on Hostinger Api

AI agents use hosting_createWebsiteSubdomainV1 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
`domain`	string	Yes	Domain name
`username`	string	Yes	username parameter
`directory`	string	—	Directory name for the subdomain relative to the website root
`subdomain`	string	Yes	Subdomain prefix to create under the selected website
`is_using_public_directory`	boolean	—	Use the website public directory as the subdomain root directory

Parameters from the server's own tool schema.

RISK

Why hosting_createWebsiteSubdomainV1 is rated Medium

This tool creates a new subdomain, which is a reversible configuration change that adds a new resource to the hosting account. It does not delete data (not Destructive), does not involve financial transactions (not Financial), and does not execute arbitrary code or system commands (not Execute). It is clearly a Write operation as it creates new infrastructure/configuration.

From the tool's definition Tool name contains 'create' and description states 'Create a new subdomain for the selected website.' This is a content/configuration creation operation that modifies the website's subdomain structure.

Risk signalsAccepts file system path (directory) · Admin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs hosting_createWebsiteSubdomainV1 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_createWebsiteSubdomainV1, this is the rule to start with:

hosting_createWebsiteSubdomainV1 Rate-limited

hosting_createWebsiteSubdomainV1 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_createWebsiteSubdomainV1": {
      "limits": [
        {
          "counter": "hosting_createwebsitesubdomainv1_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_createWebsiteSubdomainV1 call is checked against it from then on.

FAQ

Questions about hosting_createWebsiteSubdomainV1

What does the hosting_createWebsiteSubdomainV1 tool do? +

Create a new subdomain for the selected website. Provide a subdomain prefix and, optionally, a custom directory or the website public directory to use as the subdomain root. 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_createWebsiteSubdomainV1 accept? +

hosting_createWebsiteSubdomainV1 accepts 5 parameters: domain, username, directory, subdomain, is_using_public_directory. Required: domain, username, subdomain. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on hosting_createWebsiteSubdomainV1? +

Register the Hostinger Api MCP server in PolicyLayer and add a rule for hosting_createWebsiteSubdomainV1: 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_createWebsiteSubdomainV1? +

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

Can I rate-limit hosting_createWebsiteSubdomainV1? +

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

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

hosting_createWebsiteSubdomainV1 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 →