salesforce_delete_lead
AI agents call salesforce_delete_lead to permanently remove resources in Salesforce MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of CRM lead records is irreversible and destroys customer data. This is a destructive action that cannot be undone. While severity is not critical (no direct financial transactions), the high confidence in destructive categorization and the enterprise impact of losing customer relationship data justifies 'high' severity.
From the tool's definition Tool name 'salesforce_delete_lead' explicitly indicates permanent removal of lead data from Salesforce CRM. No description provided, but function name unambiguously denotes deletion operation.
Attacks that exploit this kind of access
salesforce_delete_lead. It is categorised as a Destructive tool in the Salesforce MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Salesforce MCP Server MCP server in PolicyLayer and add a rule for salesforce_delete_lead: 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 Salesforce MCP Server. Nothing to install.
salesforce_delete_lead 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 salesforce_delete_lead 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 salesforce_delete_lead. 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.
salesforce_delete_lead is provided by the Salesforce MCP Server MCP server (sowmya-rapid/salesforce-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 →