package_install · Salesforce CLI MCP Server MCP

WHAT IT DOES

What package_install does on Salesforce CLI MCP Server

AI agents use package_install to create or update resources in Salesforce CLI MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Salesforce CLI MCP Server environment.

WHY IT NEEDS A POLICY

Why package_install needs a policy

Installing or upgrading a package modifies the org's configuration and installed components. While not irreversibly destructive (packages can be uninstalled), it does introduce new code, metadata, and dependencies into the org.

From the tool's definition Install or upgrade a package version in a Salesforce org

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

package_install Rate-limited

package_install 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": {
    "package_install": {
      "limits": [
        {
          "counter": "package_install_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 package_install

What does the package_install tool do? +

Install or upgrade a package version in a Salesforce org. Supports both package IDs (04t) and aliases with various configuration options. It is categorised as a Write tool in the Salesforce CLI MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on package_install? +

Register the Salesforce CLI MCP Server MCP server in PolicyLayer and add a rule for package_install: 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 package_install? +

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

Can I rate-limit package_install? +

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

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

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