reach_listSegmentFilterAttributesV1
List every attribute a segment condition can filter on, with the operators each attribute accepts, the value format they expect and, where the value is constrained, the allowed values. The list is profile specific: it includes the profile's custom contact fields, its tags and its 20 most recently...
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/reach-listsegmentfilterattributesv1.md
What reach_listSegmentFilterAttributesV1 does on Hostinger Api
AI agents call reach_listSegmentFilterAttributesV1 to retrieve information from Hostinger Api without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
profileUuid | string | Yes | Profile uuid parameter |
Parameters from the server's own tool schema.
Why reach_listSegmentFilterAttributesV1 is rated Low
Retrieves segment filter metadata and configuration options without modifying data.
From the tool's definition List every attribute a segment condition can filter on; valid attributes cannot be hardcoded.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs reach_listSegmentFilterAttributesV1 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_listSegmentFilterAttributesV1, this is the rule to start with:
reach_listSegmentFilterAttributesV1 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 Api, apply this rule, and every reach_listSegmentFilterAttributesV1 call is checked against it from then on.
Questions about reach_listSegmentFilterAttributesV1
List every attribute a segment condition can filter on, with the operators each attribute accepts, the value format they expect and, where the value is constrained, the allowed values. The list is profile specific: it includes the profile's custom contact fields, its tags and its 20 most recently published campaigns, so the valid attributes cannot be hardcoded. Read it before creating or updating a segment to discover the valid attribute, operator and value combinations. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.
reach_listSegmentFilterAttributesV1 accepts 1 parameter: profileUuid. Required: profileUuid. 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_listSegmentFilterAttributesV1: 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_listSegmentFilterAttributesV1 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_listSegmentFilterAttributesV1 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_listSegmentFilterAttributesV1. 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_listSegmentFilterAttributesV1 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