reach_segments_contacts

List contacts in a segment.

SERVERHostinger SOURCEidugeni/hostinger-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hostinger-mcp/reach-segments-contacts.md

WHAT IT DOES

What reach_segments_contacts does on Hostinger

AI agents call reach_segments_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.

RISK

Why reach_segments_contacts is rated Low

This tool queries and returns contact data from a marketing segment. The verb 'list' is a classic read-only operation. There is no indication of data creation, modification, deletion, or execution of external operations.

From the tool's definition Tool name 'reach_segments_contacts' and description 'List contacts in a segment' indicate a data retrieval operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs reach_segments_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_contacts, this is the rule to start with:

reach_segments_contacts Allowed

reach_segments_contacts is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "reach_segments_contacts": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger, apply this rule, and every reach_segments_contacts call is checked against it from then on.

FAQ

Questions about reach_segments_contacts

What does the reach_segments_contacts tool do? +

List contacts in a segment. It is categorised as a Read tool in the Hostinger MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on reach_segments_contacts? +

Register the Hostinger MCP server in PolicyLayer and add a rule for reach_segments_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.

What risk level is reach_segments_contacts? +

reach_segments_contacts is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit reach_segments_contacts? +

Yes. Add a rate_limit block to the reach_segments_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.

How do I block reach_segments_contacts completely? +

Set action: deny in the PolicyLayer policy for reach_segments_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.

What MCP server provides reach_segments_contacts? +

reach_segments_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.

KEEP EXPLORING

More on Hostinger, and thousands of servers like it.

This server

All 284 Hostinger tools →

Across the catalogue

aiva_get_rfm_segments on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →