ecommerce_createStoreV1
Create a new store for your account. A primary sales channel is created alongside the store.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/ecommerce-createstorev1.md
What ecommerce_createStoreV1 does on Hostinger Api
AI agents use ecommerce_createStoreV1 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 |
|---|---|---|---|
name | string | — | name parameter |
language | string | — | ISO 639-1 language code. |
company_name | string | — | company_name parameter |
country_code | string | — | ISO 3166-1 alpha-2 country code. |
company_email | string | — | company_email parameter |
sales_channel | object | — | sales_channel parameter |
Parameters from the server's own tool schema.
Why ecommerce_createStoreV1 is rated Medium
This tool creates new infrastructure (a store and sales channel) for an e-commerce account. While reversible (stores can typically be deleted), the creation of a sales channel tied to billing and customer-facing operations makes this a Write operation with high severity due to potential for unauthorized store creation that could commit the account to new operational or financial obligations.
From the tool's definition Tool name 'ecommerce_createStoreV1' and description 'Create a new store for your account' indicate creation of new data/resources.
Attacks that exploit this kind of access
The rule that runs ecommerce_createStoreV1 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 ecommerce_createStoreV1, this is the rule to start with:
ecommerce_createStoreV1 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 Api, apply this rule, and every ecommerce_createStoreV1 call is checked against it from then on.
Questions about ecommerce_createStoreV1
Create a new store for your account. A primary sales channel is created alongside the store. 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.
ecommerce_createStoreV1 accepts 6 parameters: name, language, company_name, country_code, company_email, sales_channel. The full parameter table on this page comes from the server's own tool schema.
Register the Hostinger Api MCP server in PolicyLayer and add a rule for ecommerce_createStoreV1: 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.
ecommerce_createStoreV1 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 ecommerce_createStoreV1 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 ecommerce_createStoreV1. 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.
ecommerce_createStoreV1 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.
More on Hostinger Api, and thousands of servers like it.
This server
Across the catalogue