ecommerce_createPhysicalProductV1
Create a published physical product with a single variant priced in the store currency.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/ecommerce-createphysicalproductv1.md
What ecommerce_createPhysicalProductV1 does on Hostinger Api
AI agents use ecommerce_createPhysicalProductV1 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 | Yes | The product name. |
price | integer | Yes | Price in the smallest currency unit (e.g. cents). Must be positive. |
currency | string | — | ISO 4217 currency code. Defaults to the store's default currency when omitted. |
store_id | string | Yes | The ID of the store to create the product in. |
description | string | — | The product description. |
Parameters from the server's own tool schema.
Why ecommerce_createPhysicalProductV1 is rated Medium
This tool creates new product entries in an e-commerce system, which is a write operation that modifies data. While it creates published products (making them visible), the action is reversible through deletion or modification.
From the tool's definition Tool name contains 'create' and description states 'Create a published physical product' which creates new data in the e-commerce store. This is a reversible write operation that modifies store inventory/product catalog.
Attacks that exploit this kind of access
The rule that runs ecommerce_createPhysicalProductV1 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_createPhysicalProductV1, this is the rule to start with:
ecommerce_createPhysicalProductV1 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_createPhysicalProductV1 call is checked against it from then on.
Questions about ecommerce_createPhysicalProductV1
Create a published physical product with a single variant priced in the store currency. 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_createPhysicalProductV1 accepts 5 parameters: name, price, currency, store_id, description. Required: name, price, store_id. 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_createPhysicalProductV1: 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_createPhysicalProductV1 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_createPhysicalProductV1 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_createPhysicalProductV1. 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_createPhysicalProductV1 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