sf_list_sandboxes
Lists all sandbox orgs associated with the production org, including their status, license type, and dates. Returns data from the SandboxInfo Tooling API object. Use this to monitor sandbox creation and refresh status. Must be called from the production org.
This record as markdown: /tools/io-github-semwalajay83-sem-salesforce-metadata-mcp/sf-list-sandboxes.md
What sf_list_sandboxes does on Salesforce Metadata Mcp
AI agents call sf_list_sandboxes to retrieve information from Salesforce Metadata Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why sf_list_sandboxes is rated Low
This tool retrieves and queries sandbox metadata from Salesforce's Tooling API without any side effects. It is a pure read operation that returns organizational information about sandbox environments. The blast radius is minimal—misuse would only expose sandbox configuration details, not cause modifications or data loss.
From the tool's definition Tool 'sf_list_sandboxes' uses 'Lists' and 'Returns data' language, describing a query operation against the SandboxInfo Tooling API object. No modification, execution, deletion, or financial operation is indicated.
Attacks that exploit this kind of access
The rule that runs sf_list_sandboxes 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_list_sandboxes, this is the rule to start with:
sf_list_sandboxes is read-only, so it stays allowed. 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_list_sandboxes call is checked against it from then on.
Questions about sf_list_sandboxes
Lists all sandbox orgs associated with the production org, including their status, license type, and dates. Returns data from the SandboxInfo Tooling API object. Use this to monitor sandbox creation and refresh status. Must be called from the production org. It is categorised as a Read tool in the Salesforce Metadata Mcp MCP Server, which means it retrieves data without modifying state.
Register the Salesforce Metadata MCP server in PolicyLayer and add a rule for sf_list_sandboxes: 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_list_sandboxes is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the sf_list_sandboxes 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_list_sandboxes. 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_list_sandboxes 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.
This server
Across the catalogue