Deploy a metadata bundle (e.g., LWC) from a directory path
AI agents invoke deploy-bundle to trigger actions in Salesforce 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.
While not inherently destructive or financial, metadata deployment is an Execute action because it triggers external operations (Salesforce deployment process) whose effects are dependent on the bundle contents and target environment. This carries high severity due to potential for wide-ranging impact on org functionality, user workflows, and data integrity if malicious or incorrect metadata is deployed.
From the tool's definition Tool deploys metadata bundle from directory path to Salesforce production or sandbox environment. Metadata deployment executes code changes, configuration updates, and system modifications that can affect application behavior, user access, and business logic…
Documented attack patterns abuse exactly the kind of access deploy-bundle gives an agent:
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-bundle:
{
"version": "1",
"default": "deny",
"tools": {
"deploy-bundle": {
"limits": [
{
"counter": "deploy-bundle_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}deploy-bundle 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.
Free to start. No card required.
Deploy a metadata bundle (e.g., LWC) from a directory path. 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.
Register the Salesforce MCP Server MCP server in PolicyLayer and add a rule for deploy-bundle: 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.
deploy-bundle is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the deploy-bundle 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.
Set action: deny in the PolicyLayer policy for deploy-bundle. 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.
deploy-bundle 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.
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.
Free to start. No card required.
17 Salesforce MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.