reach_listProfileContactsV1
Get a paginated list of contacts belonging to a profile. Contacts can be filtered by subscription status, by tag, and by an email search term. The meta.total field of the response is the number of contacts matching the filters, so calling this endpoint without filters gives the profile's total co...
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/reach-listprofilecontactsv1.md
What reach_listProfileContactsV1 does on Hostinger Api
AI agents call reach_listProfileContactsV1 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 |
search | string | — | Search contacts by email |
per_page | integer | — | Number of items per page |
tag_uuid | string | — | Filter contacts by tag UUID |
profileUuid | string | Yes | Profile uuid parameter |
subscription_status | string | — | Filter contacts by subscription status |
Parameters from the server's own tool schema.
Why reach_listProfileContactsV1 is rated Low
Retrieves contact data without modification or side effects; read-only query operation.
From the tool's definition Get a paginated list of contacts belonging to a profile.
Attacks that exploit this kind of access
The rule that runs reach_listProfileContactsV1 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_listProfileContactsV1, this is the rule to start with:
reach_listProfileContactsV1 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_listProfileContactsV1 call is checked against it from then on.
Questions about reach_listProfileContactsV1
Get a paginated list of contacts belonging to a profile. Contacts can be filtered by subscription status, by tag, and by an email search term. The meta.total field of the response is the number of contacts matching the filters, so calling this endpoint without filters gives the profile's total contact count. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.
reach_listProfileContactsV1 accepts 6 parameters: page, search, per_page, tag_uuid, profileUuid, subscription_status. 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_listProfileContactsV1: 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_listProfileContactsV1 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_listProfileContactsV1 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_listProfileContactsV1. 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_listProfileContactsV1 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