Critical-risk tools in Salesforce Metadata Mcp
5 of the 229 tools in Salesforce Metadata Mcp are classified as critical risk. This page profiles those tools specifically, with recommended policy actions and the attack patterns that target them.
Every operation listed below is an action PolicyLayer recommends controlling at the transport layer. Open any tool to see the full profile, risk score, and YAML policy snippet.
Tools at critical risk
-
sf_bulk_delete_recordsDestructiveDeletes multiple records by ID asynchronously using Salesforce Bulk API 2.0. Returns a job ID to track status. Use with caution — deleted records go to the Recycle Bin. objectA...
-
sf_delete_metadataDestructivePermanently deletes one or more metadata components of a given type via the Metadata API
-
sf_delete_recordDestructiveDeletes a single SObject record by record ID via the Salesforce REST API. The deletion is permanent and cannot be undone (the record goes to the Recycle Bin for objects that sup...
-
sf_delete_scratch_orgDestructiveDeletes a Salesforce scratch org by alias. This permanently removes the org and all its data. Use when finished with development or testing to free up scratch org allocations. ...
-
sf_uninstall_packageDestructiveUninstalls a second-generation package from a target org using the SF CLI. Removes all metadata delivered by the package. Use before reinstalling a broken package, or to clean u...
Attacks that target this class
Critical-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.