ecommerce_updateSalesChannelV1

Update a custom sales channel. The merchant-facing name and the public url (returned as the channel domain) can be changed. Pass null to clear a value.

SERVERHostinger Api SOURCEhostinger-api-mcp

Medium RISK CLASS

Category Write

Parameters 42 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-updatesaleschannelv1.md

WHAT IT DOES

What ecommerce_updateSalesChannelV1 does on Hostinger Api

AI agents use ecommerce_updateSalesChannelV1 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	—	Public address where the custom sales channel lives. Pass null to clear it.
`name`	string	—	Merchant-facing custom name shown in the sales channels list. Pass null to clear it.
`store_id`	string	Yes	The ID of the store that owns the sales channel.
`sales_channel_id`	string	Yes	The ID of the sales channel to update.

Parameters from the server's own tool schema.

RISK

Why ecommerce_updateSalesChannelV1 is rated Medium

This tool creates or modifies data reversibly by updating sales channel configurations. It does not delete (would be Destructive), execute code (would be Execute), or move money (would be Financial). The ability to modify public URLs and channel names presents medium severity risk if misused by an agent, as it could alter e-commerce configurations and affect customer-facing properties, but changes are reversible.

From the tool's definition Tool description explicitly states 'Update a custom sales channel' and allows changing merchant-facing 'name' and public 'url' properties. 'Pass `null` to clear a value' indicates reversible modification.

Risk signalsAccepts URL/endpoint input (url)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

ecommerce_updateSalesChannelV1 Rate-limited

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

FAQ

Questions about ecommerce_updateSalesChannelV1

What does the ecommerce_updateSalesChannelV1 tool do? +

Update a custom sales channel. The merchant-facing name and the public url (returned as the channel domain) can be changed. Pass null to clear a value. 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_updateSalesChannelV1 accept? +

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

How do I enforce a policy on ecommerce_updateSalesChannelV1? +

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

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

Can I rate-limit ecommerce_updateSalesChannelV1? +

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

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

ecommerce_updateSalesChannelV1 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 238 Hostinger Api tools →

Across the catalogue

The MCP Attack Database →

Guides

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