ecommerce_listStorePaymentProvidersV1
List a store's payment providers, split into providers already connected to the store and gateways available to install. Never exposes gateway credentials, secrets, or configuration.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/ecommerce-liststorepaymentprovidersv1.md
What ecommerce_listStorePaymentProvidersV1 does on Hostinger Api
AI agents call ecommerce_listStorePaymentProvidersV1 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 payment providers for. |
include_currency_unsupported | boolean | — | Include gateways that do not support the store currency in the available list. |
Parameters from the server's own tool schema.
Why ecommerce_listStorePaymentProvidersV1 is rated Low
Tool retrieves payment provider information without exposing sensitive data or enabling modifications.
From the tool's definition List a store's payment providers; never exposes credentials, secrets, or configuration.
Attacks that exploit this kind of access
The rule that runs ecommerce_listStorePaymentProvidersV1 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_listStorePaymentProvidersV1, this is the rule to start with:
ecommerce_listStorePaymentProvidersV1 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_listStorePaymentProvidersV1 call is checked against it from then on.
Questions about ecommerce_listStorePaymentProvidersV1
List a store's payment providers, split into providers already connected to the store and gateways available to install. Never exposes gateway credentials, secrets, or configuration. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.
ecommerce_listStorePaymentProvidersV1 accepts 2 parameters: store_id, include_currency_unsupported. 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_listStorePaymentProvidersV1: 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_listStorePaymentProvidersV1 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_listStorePaymentProvidersV1 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_listStorePaymentProvidersV1. 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_listStorePaymentProvidersV1 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