sf_export_omnistudio_component

Exports an OmniStudio component

SERVERSalesforce Metadata Mcp SOURCEsalesforce-metadata-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee 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-export-omnistudio-component.md

WHAT IT DOES

What sf_export_omnistudio_component does on Salesforce Metadata Mcp

AI agents call sf_export_omnistudio_component 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.

RISK

Why sf_export_omnistudio_component is rated Low

Exporting a component is a read operation that retrieves/extracts existing data without modifying or deleting anything. The blast radius is low as it only reads metadata.

From the tool's definition 'Exports an OmniStudio component' — export/read operation that retrieves component data

Attacks that exploit this kind of access

RECOMMENDED RULE

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

sf_export_omnistudio_component Allowed

sf_export_omnistudio_component is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sf_export_omnistudio_component": {}
  }
}

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

FAQ

Questions about sf_export_omnistudio_component

What does the sf_export_omnistudio_component tool do? +

Exports an OmniStudio component. It is categorised as a Read tool in the Salesforce Metadata Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on sf_export_omnistudio_component? +

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

sf_export_omnistudio_component is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit sf_export_omnistudio_component? +

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

Set action: deny in the PolicyLayer policy for sf_export_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_export_omnistudio_component? +

sf_export_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

Roll out MCP under one policy →Data exfiltration →MCP token cost →