ecommerce_listStoreOrdersV1

SERVERHostinger Api SOURCEhostinger-api-mcp

Low RISK CLASS

Category Read

Parameters 101 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/ecommerce-liststoreordersv1.md

WHAT IT DOES

What ecommerce_listStoreOrdersV1 does on Hostinger Api

AI agents call ecommerce_listStoreOrdersV1 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
`q`	string	—	Free-text search over customer name, email, order number and line items.
`page`	integer	—	Page number
`email`	string	—	Customer email, matched exactly.
`status`	array	—	Order statuses to include.
`store_id`	string	Yes	The ID of the store to list orders for.
`display_id`	string	—	The order number the merchant and customer see.
`created_at_to`	string	—	Latest creation time to include, inclusive. A bare date covers that whole day.
`payment_status`	array	—	Payment statuses to include. A paid order is "captured".
`created_at_from`	string	—	Earliest creation time to include, inclusive. Accepts a date or ISO date-time (UTC).
`fulfillment_status`	array	—	Fulfilment statuses to include.

Parameters from the server's own tool schema.

RISK

Why ecommerce_listStoreOrdersV1 is rated Low

Retrieves order data with filters; no modifications, deletions, or financial transactions executed.

From the tool's definition List store orders, filter by status, payment, customer email, order number

Risk signalsHigh parameter count (10 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

ecommerce_listStoreOrdersV1 Allowed

ecommerce_listStoreOrdersV1 is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ecommerce_listStoreOrdersV1": {}
  }
}

ALLOW ONLY 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_listStoreOrdersV1 call is checked against it from then on.

FAQ

Questions about ecommerce_listStoreOrdersV1

What does the ecommerce_listStoreOrdersV1 tool do? +

List a store's orders newest first as summaries. Filter by status, payment or fulfilment status, customer email, order number or a free-text query. Amounts are in the smallest currency unit. Retrieve a single order for its line items, addresses and fulfilments. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.

What parameters does ecommerce_listStoreOrdersV1 accept? +

ecommerce_listStoreOrdersV1 accepts 10 parameters: q, page, email, status, store_id, display_id, created_at_to, payment_status, created_at_from, fulfillment_status. Required: 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_listStoreOrdersV1? +

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

ecommerce_listStoreOrdersV1 is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit ecommerce_listStoreOrdersV1? +

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

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

ecommerce_listStoreOrdersV1 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 382 Hostinger Api tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →