request_profile_deletion
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.
The tool name explicitly references deletion of a profile, which is an irreversible destructive action. Customer profile data, once deleted, typically cannot be recovered. The empty description lowers confidence slightly, but the naming convention and sibling tools ('delete_profile') strongly support a Destructive classification.
From the tool's definition Tool name 'request_profile_deletion' clearly indicates deletion of a profile. Sibling tool 'delete_profile' confirms this server pattern of destructive operations on profiles.
Attacks that exploit this kind of access
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 (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 →