AI agents call manage_segments to retrieve information from Kit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool explicitly states it is read-only and only supports a list action, retrieving segment data without any side effects or modifications.
From the tool's definition "List Kit subscriber segments (read-only — segments are created in the Kit UI). Actions: list"
Attacks that exploit this kind of access
List Kit subscriber segments (read-only — segments are created in the Kit UI). Actions: list. It is categorised as a Read tool in the Kit MCP Server, which means it retrieves data without modifying state.
Register the Kit MCP server in PolicyLayer and add a rule for manage_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 Kit. Nothing to install.
manage_segments 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 manage_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.
Set action: deny in the PolicyLayer policy for manage_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.
manage_segments is provided by the Kit MCP server (@dancumberland/kit-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →