AI agents call request_profile_deletion 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.
Despite the empty description, 'request_profile_deletion' almost certainly initiates a deletion of a user profile, which is irreversible. Profile data loss is a high-impact action. The presence of 'delete_profile' as a sibling tool on the same server corroborates that profile deletion is supported. Classified as Destructive with critical severity due to the potential permanent loss of customer profile data.
From the tool's definition Tool name 'request_profile_deletion' strongly implies irreversible deletion of a user profile. Sibling tool 'delete_profile' confirms the server supports destructive profile operations.
Documented attack patterns abuse exactly the kind of access request_profile_deletion gives an agent:
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 request_profile_deletion:
{
"version": "1",
"default": "deny",
"hide": [
"request_profile_deletion"
]
}request_profile_deletion disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
request_profile_deletion. 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.
Register the Klaviyo MCP Server MCP server in PolicyLayer and add a rule for request_profile_deletion: 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.
request_profile_deletion is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the request_profile_deletion 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 request_profile_deletion. 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.
request_profile_deletion 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.
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.