sf_import_omnistudio_component

SERVERSalesforce Metadata Mcp SOURCEsalesforce-metadata-mcp

Medium RISK CLASS

Category Write

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-import-omnistudio-component.md

WHAT IT DOES

What sf_import_omnistudio_component does on Salesforce Metadata Mcp

AI agents use sf_import_omnistudio_component 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.

RISK

Why sf_import_omnistudio_component is rated Medium

This tool creates new components or modifies existing ones by importing from JSON, which is a reversible Write operation. It does not execute code directly (Execute), delete irreversibly (Destructive), or move money (Financial).

From the tool's definition Imports an OmniStudio component into the org from previously exported JSON...Optionally renames the component on import.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

sf_import_omnistudio_component Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sf_import_omnistudio_component": {
      "limits": [
        {
          "counter": "sf_import_omnistudio_component_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_import_omnistudio_component call is checked against it from then on.

FAQ

Questions about sf_import_omnistudio_component

What does the sf_import_omnistudio_component tool do? +

Imports an OmniStudio component into the org from previously exported JSON (from sf_export_omnistudio_component). Optionally renames the component on import. componentType: FlexCard, OmniScript, DataRaptor, IntegrationProcedure, CalculationMatrix, or CalculationProcedure exportedJson: the JSON string returned by sf_export_omnistudio_component newComponentName: optional new name/fullName for the imported component (useful when migrating to a different name). 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.

How do I enforce a policy on sf_import_omnistudio_component? +

Register the Salesforce Metadata MCP server in PolicyLayer and add a rule for sf_import_omnistudio_component: 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_import_omnistudio_component? +

sf_import_omnistudio_component is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit sf_import_omnistudio_component? +

Yes. Add a rate_limit block to the sf_import_omnistudio_component 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_import_omnistudio_component completely? +

Set action: deny in the PolicyLayer policy for sf_import_omnistudio_component. 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_import_omnistudio_component? +

sf_import_omnistudio_component 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 →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →