reach_segments_profile_contacts
List contacts for a segment within a specific profile.
This record as markdown: /tools/hostinger-mcp/reach-segments-profile-contacts.md
What reach_segments_profile_contacts does on Hostinger
AI agents call reach_segments_profile_contacts to retrieve information from Hostinger without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why reach_segments_profile_contacts is rated Low
This tool retrieves/queries contact information from a segment profile. There are no side effects, data modifications, or destructive operations described. The action is passive data retrieval, fitting the 'Read' category. Severity is low because unauthorized access to contact lists, while a privacy concern, typically does not have the operational blast radius of write, execute, or destructive operations.
From the tool's definition Tool name 'reach_segments_profile_contacts' and description 'List contacts for a segment within a specific profile' indicate a data retrieval operation. The verb 'List' is characteristic of read-only operations that query existing data without modification.
Attacks that exploit this kind of access
The rule that runs reach_segments_profile_contacts safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hostinger, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For reach_segments_profile_contacts, this is the rule to start with:
reach_segments_profile_contacts 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, apply this rule, and every reach_segments_profile_contacts call is checked against it from then on.
Questions about reach_segments_profile_contacts
List contacts for a segment within a specific profile. It is categorised as a Read tool in the Hostinger MCP Server, which means it retrieves data without modifying state.
Register the Hostinger MCP server in PolicyLayer and add a rule for reach_segments_profile_contacts: 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. Nothing to install.
reach_segments_profile_contacts 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_segments_profile_contacts 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_segments_profile_contacts. 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_segments_profile_contacts is provided by the Hostinger MCP server (idugeni/hostinger-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hostinger, and thousands of servers like it.
This server
Across the catalogue