ecommerce_setStoreShippingV1

Set the flat-rate shipping price for a store, creating the shipping zone if it does not exist yet.

SERVERHostinger Api SOURCEhostinger-api-mcp

Medium RISK CLASS

Category Write

Parameters 22 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-setstoreshippingv1.md

WHAT IT DOES

What ecommerce_setStoreShippingV1 does on Hostinger Api

AI agents use ecommerce_setStoreShippingV1 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
`price`	integer	Yes	Flat shipping rate in the smallest currency unit (e.g. cents). Use 0 for free shipping.
`store_id`	string	Yes	The ID of the store to configure shipping for.

Parameters from the server's own tool schema.

RISK

Why ecommerce_setStoreShippingV1 is rated Medium

This tool modifies e-commerce store settings by setting shipping prices and creating shipping zones. While it writes configuration data that affects business operations (and thus has medium severity due to potential impact on store functionality and customer experience), it is reversible and does not permanently delete data, commit financial transactions, or execute arbitrary code.

From the tool's definition The tool name 'ecommerce_setStoreShippingV1' and description 'Set the flat-rate shipping price for a store, creating the shipping zone if it does not exist yet' indicate a data modification operation that creates or updates shipping configuration.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

ecommerce_setStoreShippingV1 Rate-limited

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

FAQ

Questions about ecommerce_setStoreShippingV1

What does the ecommerce_setStoreShippingV1 tool do? +

Set the flat-rate shipping price for a store, creating the shipping zone if it does not exist yet. 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_setStoreShippingV1 accept? +

ecommerce_setStoreShippingV1 accepts 2 parameters: price, store_id. Required: price, 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_setStoreShippingV1? +

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

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

Can I rate-limit ecommerce_setStoreShippingV1? +

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

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

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