reach_createANewContactSegmentV1
Create a new contact segment. This endpoint allows creating a new contact segment that can be used to organize contacts. The segment can be configured with specific criteria like email, name, subscription status, etc. Deprecated. This endpoint cannot target a profile, so it always falls back to t...
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/reach-createanewcontactsegmentv1.md
What reach_createANewContactSegmentV1 does on Hostinger Api
AI agents use reach_createANewContactSegmentV1 to create or update resources in Hostinger Api, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hostinger Api environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | name parameter |
logic | string | Yes | logic parameter |
conditions | array | Yes | conditions parameter |
Parameters from the server's own tool schema.
Why reach_createANewContactSegmentV1 is rated Medium
Creates organizational data structure reversibly; moderate blast radius if misconfigured affecting contact management.
From the tool's definition Create a new contact segment; organizes contacts with specific criteria.
Attacks that exploit this kind of access
The rule that runs reach_createANewContactSegmentV1 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_createANewContactSegmentV1, this is the rule to start with:
reach_createANewContactSegmentV1 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 Api, apply this rule, and every reach_createANewContactSegmentV1 call is checked against it from then on.
Questions about reach_createANewContactSegmentV1
Create a new contact segment. This endpoint allows creating a new contact segment that can be used to organize contacts. The segment can be configured with specific criteria like email, name, subscription status, etc. Deprecated. This endpoint cannot target a profile, so it always falls back to the client's default profile and cannot create segments in any other profile. Use POST /api/reach/v1/profiles/{profileUuid}/segmentation/segments instead. It is categorised as a Write tool in the Hostinger Api MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
reach_createANewContactSegmentV1 accepts 3 parameters: name, logic, conditions. Required: name, logic, conditions. 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_createANewContactSegmentV1: 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_createANewContactSegmentV1 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_createANewContactSegmentV1 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_createANewContactSegmentV1. 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_createANewContactSegmentV1 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