salesforce_delete_record
Delete a Salesforce record
This record as markdown: /tools/io-github-alifanov-scopegate/salesforce-delete-record.md
What salesforce_delete_record does on ScopeGate
AI agents call salesforce_delete_record to permanently remove resources in ScopeGate, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why salesforce_delete_record is rated Critical
Deletion of records cannot be undone and represents permanent data loss. Even with granular permission controls in place, a compromised agent or misguided instruction could cause significant business harm by deleting critical customer, opportunity, or account records. High severity due to the irreversible nature and potential blast radius in a CRM context.
From the tool's definition Tool name explicitly states 'delete_record' and description confirms 'Delete a Salesforce record'. This irreversibly removes data from a production system.
Attacks that exploit this kind of access
The rule that runs salesforce_delete_record safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScopeGate, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For salesforce_delete_record, this is the rule to start with:
salesforce_delete_record is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect ScopeGate, apply this rule, and every salesforce_delete_record call is checked against it from then on.
Questions about salesforce_delete_record
Delete a Salesforce record. It is categorised as a Destructive tool in the ScopeGate MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ScopeGate MCP server in PolicyLayer and add a rule for salesforce_delete_record: 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 ScopeGate. Nothing to install.
salesforce_delete_record 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_record 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_record. 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_record is provided by the ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScopeGate, and thousands of servers like it.
Across the catalogue