sf_project_deploy · Salesforce CLI MCP Server MCP

WHAT IT DOES

What sf_project_deploy does on Salesforce CLI MCP Server

AI agents invoke sf_project_deploy to trigger actions in Salesforce CLI MCP Server. 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.

WHY IT NEEDS A POLICY

Why sf_project_deploy needs a policy

This tool triggers deployment of code and configuration to a Salesforce organization, which is an irreversible execution of a complex external operation. While not purely destructive (it can be rolled back in some cases), it executes arbitrary metadata changes determined by arguments and affects a production system.

From the tool's definition Tool name 'sf_project_deploy' and description 'Deploy metadata to a Salesforce org' indicates execution of a deployment operation that modifies the target Salesforce organization.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

sf_project_deploy Rate-limited

sf_project_deploy 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_project_deploy": {
      "limits": [
        {
          "counter": "sf_project_deploy_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Salesforce CLI MCP Server, so you can run agents against it safely.

FAQ

Questions about sf_project_deploy

What does the sf_project_deploy tool do? +

Deploy metadata to a Salesforce org. It is categorised as a Execute tool in the Salesforce CLI MCP Server 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_project_deploy? +

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

What risk level is sf_project_deploy? +

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

Can I rate-limit sf_project_deploy? +

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

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

sf_project_deploy is provided by the Salesforce CLI MCP Server MCP server (timaw513-emergenit/salesforce-cli-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.