sf_deactivate_flow
Deactivates the currently active version of a Flow via the Tooling API, setting its status to Draft. This stops the flow from being triggered. Use sf_activate_flow to re-activate a specific version. Note: deactivating a flow does not delete it.
This record as markdown: /tools/io-github-semwalajay83-sem-salesforce-metadata-mcp/sf-deactivate-flow.md
What sf_deactivate_flow does on Salesforce Metadata Mcp
AI agents invoke sf_deactivate_flow 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_deactivate_flow is rated High
This tool triggers an external operation (via Tooling API) that changes the operational state of a Salesforce Flow, stopping it from being triggered. It is not a simple data write — it affects system behavior and automation execution. While reversible (can re-activate), the act of stopping a live business process flow can have significant operational impact, warranting high severity.
From the tool's definition 'Deactivates the currently active version of a Flow via the Tooling API, setting its status to Draft. This stops the flow from being triggered.'
Attacks that exploit this kind of access
The rule that runs sf_deactivate_flow 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_deactivate_flow, this is the rule to start with:
sf_deactivate_flow 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_deactivate_flow call is checked against it from then on.
Questions about sf_deactivate_flow
Deactivates the currently active version of a Flow via the Tooling API, setting its status to Draft. This stops the flow from being triggered. Use sf_activate_flow to re-activate a specific version. Note: deactivating a flow does not delete it. 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_deactivate_flow: 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_deactivate_flow 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_deactivate_flow 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_deactivate_flow. 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_deactivate_flow 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