ecommerce_listSalesChannelsV1
List a store's active sales channels with their full metadata.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/ecommerce-listsaleschannelsv1.md
What ecommerce_listSalesChannelsV1 does on Hostinger Api
AI agents call ecommerce_listSalesChannelsV1 to retrieve information from Hostinger Api without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
store_id | string | Yes | The ID of the store to list sales channels for. |
Parameters from the server's own tool schema.
Why ecommerce_listSalesChannelsV1 is rated Low
This tool retrieves and queries existing sales channel data without side effects. It performs a read-only operation to enumerate sales channels and their metadata, which is characteristic of the Read category. The low severity reflects minimal blast radius if misused by an AI agent, as it only exposes existing configuration data without enabling modifications or destructive actions.
From the tool's definition Tool name contains 'list' and description states 'List a store's active sales channels with their full metadata' — a retrieval operation with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
The rule that runs ecommerce_listSalesChannelsV1 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_listSalesChannelsV1, this is the rule to start with:
ecommerce_listSalesChannelsV1 is read-only, so it stays allowed. 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_listSalesChannelsV1 call is checked against it from then on.
Questions about ecommerce_listSalesChannelsV1
List a store's active sales channels with their full metadata. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.
ecommerce_listSalesChannelsV1 accepts 1 parameter: store_id. Required: 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_listSalesChannelsV1: 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_listSalesChannelsV1 is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the ecommerce_listSalesChannelsV1 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_listSalesChannelsV1. 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_listSalesChannelsV1 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