Create a new Salesforce package
AI agents use sf_package_create 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.
Creating a Salesforce package modifies the org's metadata and configuration state. This is a Write operation rather than Read (it creates, not retrieves). It is not Destructive because package creation is reversible and does not irreversibly delete data. It is not Execute because it does not run arbitrary code or scripts—it instantiates a defined artifact.
From the tool's definition Tool name 'sf_package_create' and description 'Create a new Salesforce package' indicate this creates a new artifact in a Salesforce org.
Attacks that exploit this kind of access
Create a new Salesforce package. 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.
Register the Salesforce CLI MCP Server MCP server in PolicyLayer and add a rule for sf_package_create: 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.
sf_package_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the sf_package_create 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 sf_package_create. 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.
sf_package_create 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →