deploy-metadata

THE RISK

High Risk

Why deploy-metadata needs a policy

This tool executes a deployment operation against a Salesforce organization, making it an Execute-category tool rather than Write. While deployments modify data/configuration, they are fundamentally execution triggers whose effects are determined by the contents of the deployed metadata bundle.

From the tool's definition Tool description states 'Deploy metadata components to Salesforce org'. Deployment of metadata is an executing operation that triggers external Salesforce organization changes, including configuration, code, and structural changes that depend on the metadata…

Documented attack patterns abuse exactly the kind of access deploy-metadata gives an agent:

POLICY

How to control deploy-metadata

PolicyLayer is an MCP gateway — it sits between your AI agents and Salesforce MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for deploy-metadata:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "deploy-metadata": {
      "limits": [
        {
          "counter": "deploy-metadata_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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.

Create a free account and register Salesforce MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Salesforce MCP Server tools

Destructive delete-record Delete records by ID(s) with auto-bulk switching Execute deploy-bundle Deploy a metadata bundle (e.g., LWC) from a directory path Execute execute-apex Execute anonymous Apex code with debug log capture Execute execute-soql Execute SOQL query with auto-bulk switching for large result sets Execute execute-sosl Execute SOSL search with multi-object support Execute run-apex-tests Run Apex tests with coverage and detailed results Write create-record Create single or multiple records with auto-bulk switching Write update-record Update single or multiple records with auto-bulk switching

All 17 Salesforce MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Salesforce MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about deploy-metadata

What does the deploy-metadata tool do? +

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

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

What risk level is deploy-metadata? +

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

Can I rate-limit deploy-metadata? +

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

Set action: deny in the PolicyLayer policy for 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 deploy-metadata? +

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

Enforce policy on every Salesforce MCP Server tool call.

Start from Salesforce MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →