sf_create_flow

SERVERSalesforce Metadata Mcp SOURCEsalesforce-metadata-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-semwalajay83-sem-salesforce-metadata-mcp/sf-create-flow.md

WHAT IT DOES

What sf_create_flow does on Salesforce Metadata Mcp

AI agents invoke sf_create_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.

RISK

Why sf_create_flow is rated High

This tool deploys executable automation logic (Flows) into a Salesforce org, which can trigger side effects including record creation, deletion, email sending, and Apex code execution. While it 'creates or updates' metadata (Write), the deployed artifact is executable automation that can cause cascading real-world effects including DeleteRecords (Destructive) and financial or operational consequences.

From the tool's definition Creates or updates a Salesforce Flow via the Metadata API. Supports advanced elements: Decision, GetRecords, CreateRecords, DeleteRecords, SendEmailAlert, ApexAction, Subflow, Loop, Assignment

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sf_create_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_create_flow, this is the rule to start with:

sf_create_flow Rate-limited

sf_create_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sf_create_flow": {
      "limits": [
        {
          "counter": "sf_create_flow_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Salesforce Metadata Mcp, apply this rule, and every sf_create_flow call is checked against it from then on.

FAQ

Questions about sf_create_flow

What does the sf_create_flow tool do? +

Creates or updates a Salesforce Flow via the Metadata API. Supports AutoLaunchedFlow (required for Agentforce actions), Screen Flow, RecordTriggeredFlow, and ScheduledFlow. Supports advanced elements: Decision, GetRecords, CreateRecords, DeleteRecords, SendEmailAlert, ApexAction, Subflow, Loop, Assignment, Screen via the. 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.

How do I enforce a policy on sf_create_flow? +

Register the Salesforce Metadata MCP server in PolicyLayer and add a rule for sf_create_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.

What risk level is sf_create_flow? +

sf_create_flow is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit sf_create_flow? +

Yes. Add a rate_limit block to the sf_create_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.

How do I block sf_create_flow completely? +

Set action: deny in the PolicyLayer policy for sf_create_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.

What MCP server provides sf_create_flow? +

sf_create_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.

KEEP EXPLORING

More on Salesforce Metadata, and thousands of servers like it.

This server

All 213 Salesforce Metadata tools → High-risk tools on this server →

Across the catalogue

diagram_create on Templonix Lite MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →