Manage Kit tags — list all tags, create, rename, apply/remove tags on subscribers, or list subscribers with a specific tag. Actions: list, create, update, tag_subscriber, untag_subscriber, list_subscribers
AI agents use manage_tags 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.
The tool modifies email marketing metadata by creating tags, renaming them, and applying/removing tag associations to subscribers. These are all reversible operations—tags can be deleted, subscribers can be untagged, and names can be changed again.
From the tool's definition Tool performs reversible write operations: 'create', 'rename', 'tag_subscriber', 'untag_subscriber' modify subscriber metadata and tag definitions. These are not destructive (tags and associations can be removed or changed).
Attacks that exploit this kind of access
Manage Kit tags — list all tags, create, rename, apply/remove tags on subscribers, or list subscribers with a specific tag. Actions: list, create, update, tag_subscriber, untag_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_tags: 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_tags 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_tags 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_tags. 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_tags 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 →