sf_create_scratch_org
Creates a Salesforce scratch org using the SF CLI. Scratch orgs are temporary, configurable environments for development and testing. Requires a Dev Hub org to be authorized. definitionFile: path to project-scratch-def.json (optional, defaults to CLI default) alias: alias for the scratch org dura...
This record as markdown: /tools/io-github-semwalajay83-sem-salesforce-metadata-mcp/sf-create-scratch-org.md
What sf_create_scratch_org does on Salesforce Metadata Mcp
AI agents invoke sf_create_scratch_org to trigger actions in Salesforce Metadata Mcp. 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 sf_create_scratch_org is rated High
This tool executes an SF CLI command to provision a new Salesforce environment. It triggers an external operation (org creation) via CLI, consuming Dev Hub org capacity/licenses. While not directly financial, misuse could exhaust scratch org limits, create unauthorized environments, or be used as a staging ground for further attacks.
From the tool's definition Creates a Salesforce scratch org using the SF CLI... Requires a Dev Hub org to be authorized
Attacks that exploit this kind of access
The rule that runs sf_create_scratch_org safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Salesforce Metadata Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sf_create_scratch_org, this is the rule to start with:
sf_create_scratch_org 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Salesforce Metadata Mcp, apply this rule, and every sf_create_scratch_org call is checked against it from then on.
Questions about sf_create_scratch_org
Creates a Salesforce scratch org using the SF CLI. Scratch orgs are temporary, configurable environments for development and testing. Requires a Dev Hub org to be authorized. definitionFile: path to project-scratch-def.json (optional, defaults to CLI default) alias: alias for the scratch org duration: number of days before expiry (1–30) devHubAlias: Dev Hub org alias. It is categorised as a Execute tool in the Salesforce Metadata Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Salesforce Metadata MCP server in PolicyLayer and add a rule for sf_create_scratch_org: 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 Metadata Mcp. Nothing to install.
sf_create_scratch_org 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 sf_create_scratch_org 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_create_scratch_org. 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_create_scratch_org is provided by the Salesforce Metadata MCP server (salesforce-metadata-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Salesforce Metadata, and thousands of servers like it.
Across the catalogue