ecommerce_fulfilAnOrderV1
Create a fulfilment for the order and attach tracking in one call. Omit items to fulfil every remaining unfulfilled item. Returns the updated order summary.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/ecommerce-fulfilanorderv1.md
What ecommerce_fulfilAnOrderV1 does on Hostinger Api
AI agents use ecommerce_fulfilAnOrderV1 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 |
|---|---|---|---|
items | array | — | Line items to fulfil. Omit to fulfil every remaining unfulfilled item. |
order_id | string | Yes | The ID of the order to fulfil. |
store_id | string | Yes | The ID of the store that owns the order. |
tracking_url | string | — | Public tracking URL for the shipment. Requires tracking_number. |
notify_customer | boolean | — | Whether to email the customer about the fulfilment. Defaults to true. |
tracking_number | string | — | Carrier tracking number for the shipment. |
Parameters from the server's own tool schema.
Why ecommerce_fulfilAnOrderV1 is rated Medium
Creates fulfillment records and tracking data for orders, modifying order state irreversibly within e-commerce system.
From the tool's definition Create a fulfilment for the order and attach tracking in one call.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs ecommerce_fulfilAnOrderV1 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_fulfilAnOrderV1, this is the rule to start with:
ecommerce_fulfilAnOrderV1 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger Api, apply this rule, and every ecommerce_fulfilAnOrderV1 call is checked against it from then on.
Questions about ecommerce_fulfilAnOrderV1
Create a fulfilment for the order and attach tracking in one call. Omit items to fulfil every remaining unfulfilled item. Returns the updated order summary. 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.
ecommerce_fulfilAnOrderV1 accepts 6 parameters: items, order_id, store_id, tracking_url, notify_customer, tracking_number. 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_fulfilAnOrderV1: 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_fulfilAnOrderV1 is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the ecommerce_fulfilAnOrderV1 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_fulfilAnOrderV1. 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_fulfilAnOrderV1 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