ecommerce_retrieveAnOrderV1
Retrieve one order in full: line items (each with the id the fulfil endpoint needs), addresses, the totals breakdown and fulfilments with tracking. Amounts are in the smallest currency unit.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/ecommerce-retrieveanorderv1.md
What ecommerce_retrieveAnOrderV1 does on Hostinger Api
AI agents call ecommerce_retrieveAnOrderV1 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 |
|---|---|---|---|
order_id | string | Yes | The ID of the order to retrieve. |
store_id | string | Yes | The ID of the store that owns the order. |
Parameters from the server's own tool schema.
Why ecommerce_retrieveAnOrderV1 is rated Low
Tool retrieves order data without modification, side effects, or financial transactions.
From the tool's definition Retrieve one order in full: line items, addresses, totals, fulfilments.
Attacks that exploit this kind of access
The rule that runs ecommerce_retrieveAnOrderV1 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_retrieveAnOrderV1, this is the rule to start with:
ecommerce_retrieveAnOrderV1 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_retrieveAnOrderV1 call is checked against it from then on.
Questions about ecommerce_retrieveAnOrderV1
Retrieve one order in full: line items (each with the id the fulfil endpoint needs), addresses, the totals breakdown and fulfilments with tracking. Amounts are in the smallest currency unit. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.
ecommerce_retrieveAnOrderV1 accepts 2 parameters: order_id, store_id. Required: order_id, 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_retrieveAnOrderV1: 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_retrieveAnOrderV1 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_retrieveAnOrderV1 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_retrieveAnOrderV1. 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_retrieveAnOrderV1 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