Critical Risk →

delete_profile

delete_profile

How to control delete_profile ↓

What delete_profile does on Klaviyo MCP Server

AI agents call delete_profile to permanently remove resources in Klaviyo MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why delete_profile needs a policy

The tool name explicitly uses 'delete', which is a destructive operation that permanently removes profile data and cannot be undone. While the description is empty, the name combined with the Klaviyo context (managing customer profiles/lists) and sibling tools (create_profile, add_profiles_to_list) makes the destructive intent clear.

From the tool's definition Tool name is 'delete_profile' which indicates permanent removal of customer profile data. The verb 'delete' combined with Klaviyo's context (email marketing platform managing customer profiles) indicates irreversible data deletion.

Documented attack patterns abuse exactly the kind of access delete_profile gives an agent:

How to control delete_profile

PolicyLayer is an MCP gateway — it sits between your AI agents and Klaviyo MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_profile:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_profile"
  ]
}

delete_profile disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Klaviyo MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete_profile

What does the delete_profile tool do? +

delete_profile. It is categorised as a Destructive tool in the Klaviyo MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_profile? +

Register the Klaviyo MCP Server MCP server in PolicyLayer and add a rule for delete_profile: 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.

What risk level is delete_profile? +

delete_profile is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_profile? +

Yes. Add a rate_limit block to the delete_profile 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.

How do I block delete_profile completely? +

Set action: deny in the PolicyLayer policy for delete_profile. 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.

What MCP server provides delete_profile? +

delete_profile is provided by the Klaviyo MCP Server MCP server (mattcoatsworth/klaviyo-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Klaviyo MCP Server tool call.

Start from Klaviyo MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

41 Klaviyo MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.