add_profiles_to_list
AI agents use add_profiles_to_list to create or update resources in Klaviyo MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Klaviyo MCP Server environment.
Adding profiles to a list is a Write operation—it modifies customer list membership data reversibly (profiles can be removed). It is not Read (causes side effects), not Execute (doesn't run arbitrary code), not Destructive (reversible), not Financial (doesn't move money).
From the tool's definition Tool name 'add_profiles_to_list' indicates it adds/modifies list membership. Context shows this is a Klaviyo marketing automation server with sibling tools like create_profile, create_list, and delete_profile.
Attacks that exploit this kind of access
add_profiles_to_list. It is categorised as a Write tool in the Klaviyo MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Klaviyo MCP Server MCP server in PolicyLayer and add a rule for add_profiles_to_list: 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.
add_profiles_to_list 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 add_profiles_to_list 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 add_profiles_to_list. 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.
add_profiles_to_list is provided by the Klaviyo MCP Server MCP server (ivan-rivera-projects/klaviyo-mcp-server-enhanced). 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 →