This record as markdown: /tools/hostinger-mcp/reach-segments-create.md
What reach_segments_create does on Hostinger
AI agents use reach_segments_create to create or update resources in Hostinger, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hostinger environment.
Why reach_segments_create is rated Medium
This tool creates a new contact segment, which is a reversible write operation that modifies customer data structures. It does not delete, execute arbitrary code, or move funds. The severity is medium because creating segments could affect marketing campaigns or customer targeting, with potential for unintended audience impacts if misused by an AI agent, but the operation is reversible.
From the tool's definition Tool name 'reach_segments_create' and description 'Create a new contact segment' indicate a data creation operation that modifies contact/audience data in the Hostinger platform.
Attacks that exploit this kind of access
The rule that runs reach_segments_create 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_create, this is the rule to start with:
reach_segments_create stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_create call is checked against it from then on.
Questions about reach_segments_create
Create a new contact segment. It is categorised as a Write tool in the Hostinger MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Hostinger MCP server in PolicyLayer and add a rule for reach_segments_create: 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_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the reach_segments_create 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_create. 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_create 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