ecommerce_createCustomSalesChannelV1

Create a custom sales channel for a store. Build your own frontend and keep your catalog, orders, shipping and payments in sync through the Ecommerce API.

SERVERHostinger Api SOURCEhostinger-api-mcp

Medium RISK CLASS

Category Write

Parameters 43 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/ecommerce-createcustomsaleschannelv1.md

WHAT IT DOES

What ecommerce_createCustomSalesChannelV1 does on Hostinger Api

AI agents use ecommerce_createCustomSalesChannelV1 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
`url`	string	—	Optional public address where the custom sales channel lives.
`name`	string	Yes	Merchant-facing custom name shown in the sales channels list.
`type`	string	Yes	Sales channel type. Only "custom" channels can be created via the API.
`store_id`	string	Yes	The ID of the store to create the sales channel for.

Parameters from the server's own tool schema.

RISK

Why ecommerce_createCustomSalesChannelV1 is rated Medium

This tool creates a new resource (sales channel) that modifies the store configuration and can affect business operations including orders, shipping, and payments. While not destructive (reversible), not financial (no money moved directly), and not executing arbitrary code, it is a Write operation that establishes infrastructure affecting critical business systems.

From the tool's definition Create a custom sales channel for a store. Build your own frontend and keep your catalog, orders, shipping and payments in sync through the Ecommerce API.

Risk signalsAccepts URL/endpoint input (url)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

ecommerce_createCustomSalesChannelV1 Rate-limited

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

FAQ

Questions about ecommerce_createCustomSalesChannelV1

What does the ecommerce_createCustomSalesChannelV1 tool do? +

Create a custom sales channel for a store. Build your own frontend and keep your catalog, orders, shipping and payments in sync through the Ecommerce API. 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 ecommerce_createCustomSalesChannelV1 accept? +

ecommerce_createCustomSalesChannelV1 accepts 4 parameters: url, name, type, store_id. Required: name, type, store_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on ecommerce_createCustomSalesChannelV1? +

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

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

Can I rate-limit ecommerce_createCustomSalesChannelV1? +

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

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

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