sf_update_omniscript

Updates an existing OmniScript

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-update-omniscript.md

What sf_update_omniscript does on Salesforce Metadata Mcp

AI agents use sf_update_omniscript 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_update_omniscript is rated Medium

This tool creates or modifies data reversibly—it updates an existing OmniScript without deleting it. While reversible, the high severity reflects that OmniScripts are critical business-logic components; unauthorized modification could disrupt customer workflows, impact user experience, or expose sensitive data flows.

From the tool's definition Tool name 'sf_update_omniscript' and description 'Updates an existing OmniScript' indicate modification of configuration data.

Questions about sf_update_omniscript

What does the sf_update_omniscript tool do? +

Updates an existing OmniScript. 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_update_omniscript? +

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

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

Can I rate-limit sf_update_omniscript? +

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

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Salesforce Metadata's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.