sf_activate_flexcard
Activates an OmniStudio FlexCard so it is visible on Lightning pages and Experience Cloud sites. Reads the existing FlexCard definition and redeploys it with isActive=true. The card must already exist (created with sf_create_flexcard).
This record as markdown: /tools/io-github-semwalajay83-sem-salesforce-metadata-mcp/sf-activate-flexcard.md
What sf_activate_flexcard does on Salesforce Metadata Mcp
AI agents use sf_activate_flexcard to create or update resources in Salesforce Metadata Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Salesforce Metadata Mcp environment.
Why sf_activate_flexcard is rated Medium
This tool modifies existing metadata reversibly by changing the active state of a FlexCard. It is not destructive because the change is reversible (can be deactivated), not financial, and does not execute arbitrary code. While it affects visibility across pages, it is fundamentally a Write operation that updates component metadata.
From the tool's definition Tool 'activates' a FlexCard by redeploying it with 'isActive=true', which modifies the metadata state of an existing component to make it visible on Lightning pages and Experience Cloud sites.
Attacks that exploit this kind of access
The rule that runs sf_activate_flexcard 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_activate_flexcard, this is the rule to start with:
sf_activate_flexcard stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_activate_flexcard call is checked against it from then on.
Questions about sf_activate_flexcard
Activates an OmniStudio FlexCard so it is visible on Lightning pages and Experience Cloud sites. Reads the existing FlexCard definition and redeploys it with isActive=true. The card must already exist (created with sf_create_flexcard). It is categorised as a Write tool in the Salesforce Metadata Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Salesforce Metadata MCP server in PolicyLayer and add a rule for sf_activate_flexcard: 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_activate_flexcard is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the sf_activate_flexcard 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_activate_flexcard. 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_activate_flexcard 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