Low Risk

get_segments

get_segments

How to control get_segments ↓

What get_segments does on Klaviyo MCP Server

AI agents call get_segments to retrieve information from Klaviyo MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_segments needs a policy

The 'get_' prefix universally indicates data retrieval with no side effects. Segments in marketing platforms are query objects used to filter audiences. Retrieving segment definitions does not create, modify, delete, or execute operations. Low severity reflects that reading segment metadata poses minimal risk to the system or data integrity.

From the tool's definition Tool name 'get_segments' indicates a retrieval operation. The verb 'get' is a standard read pattern. Description is empty, but the naming convention and context within a Klaviyo marketing platform (which uses segments for audience querying) strongly suggests…

Documented attack patterns abuse exactly the kind of access get_segments gives an agent:

How to control get_segments

PolicyLayer is an MCP gateway — it sits between your AI agents and Klaviyo MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_segments:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_segments": {}
  }
}

get_segments is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Klaviyo MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_segments

What does the get_segments tool do? +

get_segments. It is categorised as a Read tool in the Klaviyo MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_segments? +

Register the Klaviyo MCP Server MCP server in PolicyLayer and add a rule for get_segments: 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 Klaviyo MCP Server. Nothing to install.

What risk level is get_segments? +

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

Can I rate-limit get_segments? +

Yes. Add a rate_limit block to the get_segments 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 get_segments completely? +

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

get_segments is provided by the Klaviyo MCP Server MCP server (mattcoatsworth/klaviyo-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Klaviyo MCP Server tool call.

Start from Klaviyo MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

41 Klaviyo MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.