hosting_listOrdersV1
Retrieve a paginated list of orders accessible to the authenticated client. This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you. Use the available query parameters to filter results by order statuses or specific...
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/hosting-listordersv1.md
What hosting_listOrdersV1 does on Hostinger Api
AI agents call hosting_listOrdersV1 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 |
|---|---|---|---|
page | integer | — | Page number |
per_page | integer | — | Number of items per page |
statuses | array | — | Filter by order statuses |
order_ids | array | — | Filter by specific order IDs |
Parameters from the server's own tool schema.
Why hosting_listOrdersV1 is rated Low
This tool retrieves and queries order information accessible to an authenticated client. It has no side effects—it does not create, modify, delete, or execute any operations. It is a straightforward data retrieval function, making it a Read category tool with low severity risk.
From the tool's definition Tool name contains 'list' and description explicitly states 'Retrieve a paginated list of orders'. The endpoint returns data without modifying, deleting, or executing operations. Query parameters are used for filtering results only.
Attacks that exploit this kind of access
The rule that runs hosting_listOrdersV1 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 hosting_listOrdersV1, this is the rule to start with:
hosting_listOrdersV1 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 hosting_listOrdersV1 call is checked against it from then on.
Questions about hosting_listOrdersV1
Retrieve a paginated list of orders accessible to the authenticated client. This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you. Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.
hosting_listOrdersV1 accepts 4 parameters: page, per_page, statuses, order_ids. 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 hosting_listOrdersV1: 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.
hosting_listOrdersV1 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 hosting_listOrdersV1 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 hosting_listOrdersV1. 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.
hosting_listOrdersV1 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