sf_add_to_change_set

SERVERSalesforce Metadata Mcp SOURCEsalesforce-metadata-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-semwalajay83-sem-salesforce-metadata-mcp/sf-add-to-change-set.md

WHAT IT DOES

What sf_add_to_change_set does on Salesforce Metadata Mcp

AI agents use sf_add_to_change_set to create or update resources in Salesforce Metadata Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Salesforce Metadata Mcp environment.

RISK

Why sf_add_to_change_set is rated Medium

This tool creates/modifies deployment artifacts (change sets) by adding metadata components, which is reversible—components can be removed from a change set before deployment. The risk is high because a malicious agent could add sensitive, broken, or malicious metadata (ApexClass, ApexTrigger, CustomField, etc.) to a change set, which would then be deployed to production or other environments if executed.

From the tool's definition Adds one or more metadata components to an existing Outbound Change Set. Change Sets are Salesforce's deployment mechanism for moving configuration and code between environments.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sf_add_to_change_set safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Salesforce Metadata Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sf_add_to_change_set, this is the rule to start with:

sf_add_to_change_set Rate-limited

sf_add_to_change_set stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sf_add_to_change_set": {
      "limits": [
        {
          "counter": "sf_add_to_change_set_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Salesforce Metadata Mcp, apply this rule, and every sf_add_to_change_set call is checked against it from then on.

FAQ

Questions about sf_add_to_change_set

What does the sf_add_to_change_set tool do? +

Adds one or more metadata components to an existing Outbound Change Set by change set name. Supports all metadata types: CustomObject, CustomField, ApexClass, ApexTrigger, Flow, ValidationRule, PermissionSet, etc. Use after creating a change set to add the metadata you want to deploy. It is categorised as a Write tool in the Salesforce Metadata Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on sf_add_to_change_set? +

Register the Salesforce Metadata MCP server in PolicyLayer and add a rule for sf_add_to_change_set: 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 Metadata Mcp. Nothing to install.

What risk level is sf_add_to_change_set? +

sf_add_to_change_set is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit sf_add_to_change_set? +

Yes. Add a rate_limit block to the sf_add_to_change_set 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.

How do I block sf_add_to_change_set completely? +

Set action: deny in the PolicyLayer policy for sf_add_to_change_set. 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.

What MCP server provides sf_add_to_change_set? +

sf_add_to_change_set is provided by the Salesforce Metadata MCP server (salesforce-metadata-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Salesforce Metadata, and thousands of servers like it.

This server

All 213 Salesforce Metadata tools →

Across the catalogue

add-tag on Kanban MCP Server →kb_add on Persistent Kb →team_manager_set_sources on Team Manager MCP →qt_set_property on Qt → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →