AI agents call delete_apex_class to permanently remove resources in Salesforce — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs an irreversible delete operation on Apex class code in Salesforce. Deletion cannot be undone without restoration from backups. This is a destructive action with significant blast radius—an AI agent invoking this without proper safeguards could permanently remove critical business logic or configurations. The cautionary language in the description reinforces the destructive nature.
From the tool's definition Tool name 'delete_apex_class' combined with description 'Delete an Apex class (use with caution)' explicitly indicates irreversible deletion of code artifacts.
Documented attack patterns abuse exactly the kind of access delete_apex_class gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Salesforce, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_apex_class:
{
"version": "1",
"default": "deny",
"hide": [
"delete_apex_class"
]
} delete_apex_class 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.
Delete an Apex class (use with caution). It is categorised as a Destructive tool in the Salesforce MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Salesforce MCP server in PolicyLayer and add a rule for delete_apex_class: 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. Nothing to install.
delete_apex_class 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 delete_apex_class 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 delete_apex_class. 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.
delete_apex_class is provided by the Salesforce MCP server (ryu-727/salesforce-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Salesforce, 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.
25 Salesforce tools catalogued and risk-classified — across an index of 43,000+ MCP servers.