sf_list_flow_versions
Lists all versions of a specific Flow, or all Flows in the org, via the Tooling API. Returns version number, status (Active, Draft, Obsolete), description, and creation date for each version. Optionally filter to exclude deactivated (Obsolete) versions. Use flowApiName to filter to a single flow.
This record as markdown: /tools/io-github-semwalajay83-sem-salesforce-metadata-mcp/sf-list-flow-versions.md
What sf_list_flow_versions does on Salesforce Metadata Mcp
AI agents call sf_list_flow_versions 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_flow_versions is rated Low
This tool queries and retrieves metadata information from Salesforce via the Tooling API without creating, modifying, or deleting any data. It is a read-only operation that gathers information about Flow versions. The blast radius of misuse is low—an agent could exfiltrate metadata information but cannot cause operational harm, data loss, or financial impact.
From the tool's definition Tool description states it 'Lists all versions of a specific Flow, or all Flows in the org' and 'Returns version number, status, description, and creation date' — purely retrieval/query operations with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs sf_list_flow_versions 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_flow_versions, this is the rule to start with:
sf_list_flow_versions 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_flow_versions call is checked against it from then on.
Questions about sf_list_flow_versions
Lists all versions of a specific Flow, or all Flows in the org, via the Tooling API. Returns version number, status (Active, Draft, Obsolete), description, and creation date for each version. Optionally filter to exclude deactivated (Obsolete) versions. Use flowApiName to filter to a single flow. 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_flow_versions: 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_flow_versions 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_flow_versions 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_flow_versions. 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_flow_versions 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