New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

reach_segments_create

Create a new contact segment.

SERVERHostinger SOURCEidugeni/hostinger-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about reach_segments_create

What does the reach_segments_create tool do? +

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.

How do I enforce a policy on reach_segments_create? +

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.

What risk level is reach_segments_create? +

reach_segments_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit reach_segments_create? +

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.

How do I block reach_segments_create completely? +

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.

What MCP server provides reach_segments_create? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Hostinger's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.