// SCAN REPORT

SegmentMCP

3 tools. 1 can modify or destroy data without limits.

1 write tool that can modify data. Rate limits recommended.

Last updated: 30 Jun 2026

1 can modify or destroy data

2 read-only

3 tools total

Community server · catalogue entry verified 30/06/2026

How to control SegmentMCP ↓

TOOL MAP

What SegmentMCP exposes to your agents

Read (2) Write / Execute (1) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous SegmentMCP tools

Write · Medium create_segment This tool creates new customer segments, which are data structures that persist in the database.

1 of SegmentMCP's 3 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control SegmentMCP

PolicyLayer is an MCP gateway — it sits between your AI agents and SegmentMCP, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "create_segment": {
    "limits": [
      {
        "counter": "create_segment_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_database_schema": {
    "limits": [
      {
        "counter": "get_database_schema_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register SegmentMCP — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON SEGMENTMCP →

Instant setup, no code required.

FULL CATALOGUE

All 3 SegmentMCP tools

WRITE 1 tools

Write create_segment Create a customer segment from natural language description (Demo Mode)

READ 2 tools

Read get_database_schema Get the current database schema information Read get_segment_info Get information about a created segment

FAQ

Questions about SegmentMCP

How do I prevent bulk modifications through SegmentMCP? +

The SegmentMCP server has 1 write tools including create_segment. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach SegmentMCP.

How many tools does the Segment MCP server expose? +

3 tools across 2 categories: Read, Write. 2 are read-only. 1 can modify, create, or delete data.

How do I enforce a policy on SegmentMCP? +

Register the Segment MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every SegmentMCP tool call.

Deterministic rules across all 3 SegmentMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON SEGMENTMCP →

Instant setup, no code required.

3 SegmentMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// WHERE THIS COMES FROM

These policies come from Segment's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

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