sf_deploy_metadata

SERVERSalesforce Metadata Mcp SOURCEsalesforce-metadata-mcp

High RISK CLASS

Category Execute

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-deploy-metadata.md

WHAT IT DOES

What sf_deploy_metadata does on Salesforce Metadata Mcp

AI agents invoke sf_deploy_metadata to trigger actions in Salesforce Metadata Mcp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why sf_deploy_metadata is rated High

This tool triggers deployment of metadata to a Salesforce organization, which is an external operation with effects depending on what metadata components are included in the deployment. While it supports validate-only mode (checkOnly:true), the primary function is to execute deployments that modify the org's state.

From the tool's definition "Deploys a set of metadata components directly to the org using the Metadata API SOAP deploy operation" and "Builds a package.xml and deployment zip in memory." This tool executes deployment operations that modify the organization's configuration and code.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sf_deploy_metadata 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_deploy_metadata, this is the rule to start with:

sf_deploy_metadata Rate-limited

sf_deploy_metadata stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_deploy_metadata": {
      "limits": [
        {
          "counter": "sf_deploy_metadata_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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_deploy_metadata call is checked against it from then on.

FAQ

Questions about sf_deploy_metadata

What does the sf_deploy_metadata tool do? +

Deploys a set of metadata components directly to the org using the Metadata API SOAP deploy operation. Builds a package.xml and deployment zip in memory. Supports validate-only (checkOnly:true) for pre-deployment validation without making changes. Specify runTests to execute test classes during deployment (required for production). Polls until complete or timeout. It is categorised as a Execute tool in the Salesforce Metadata Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on sf_deploy_metadata? +

Register the Salesforce Metadata MCP server in PolicyLayer and add a rule for sf_deploy_metadata: 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_deploy_metadata? +

sf_deploy_metadata is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit sf_deploy_metadata? +

Yes. Add a rate_limit block to the sf_deploy_metadata 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_deploy_metadata completely? +

Set action: deny in the PolicyLayer policy for sf_deploy_metadata. 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_deploy_metadata? +

sf_deploy_metadata 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 → High-risk tools on this server →

Across the catalogue

deploy_git_repo on cPanel MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →