reach_listAutomationsV1
Get a paginated list of the automations in a profile. Every automation comes with the counts of contacts that entered it, are moving through it, finished it or failed on the way. Those counts describe the contact journey and are not email engagement metrics - for opens, clicks and unsubscribes us...
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/reach-listautomationsv1.md
What reach_listAutomationsV1 does on Hostinger Api
AI agents call reach_listAutomationsV1 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 |
status | string | — | Filter automations by status. There is no `completed` status. An automation that has finished for every contact still reports `active`. |
per_page | integer | — | Number of items per page |
profileUuid | string | Yes | Profile uuid parameter |
sort_direction | string | — | Order automations by creation date. Newest first unless set to `asc`. |
Parameters from the server's own tool schema.
Why reach_listAutomationsV1 is rated Low
Tool retrieves automation metadata and contact counts without modifying data or triggering actions.
From the tool's definition Get a paginated list of the automations in a profile.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs reach_listAutomationsV1 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 reach_listAutomationsV1, this is the rule to start with:
reach_listAutomationsV1 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 reach_listAutomationsV1 call is checked against it from then on.
Questions about reach_listAutomationsV1
Get a paginated list of the automations in a profile. Every automation comes with the counts of contacts that entered it, are moving through it, finished it or failed on the way. Those counts describe the contact journey and are not email engagement metrics - for opens, clicks and unsubscribes use the campaign statistics endpoint instead. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.
reach_listAutomationsV1 accepts 5 parameters: page, status, per_page, profileUuid, sort_direction. Required: profileUuid. 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 reach_listAutomationsV1: 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.
reach_listAutomationsV1 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 reach_listAutomationsV1 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 reach_listAutomationsV1. 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.
reach_listAutomationsV1 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