AI agents use manage_sequences to create or update resources in Kit — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kit environment.
Enrolling subscribers in email sequences creates new associations and modifies subscriber state. While the operation is reversible (subscribers can be unenrolled), it affects subscriber data and can trigger automated email campaigns. The 'list' and 'list_subscribers' actions are Read operations, but the most severe capability is Write (add_subscriber).
From the tool's definition Tool description states 'enroll a subscriber' and action 'add_subscriber', which creates or modifies subscriber enrollment state in email sequences. This is a reversible write operation.
Attacks that exploit this kind of access
Manage Kit email sequences — list all sequences, enroll a subscriber, or list subscribers in a sequence. Actions: list, add_subscriber, list_subscribers. It is categorised as a Write tool in the Kit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kit MCP server in PolicyLayer and add a rule for manage_sequences: 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_sequences 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 manage_sequences 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_sequences. 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_sequences 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 →