sf_devops_promote_work_item
Promotes a DevOps Center work item to the next pipeline stage. Moving work items through the pipeline represents the progression of changes from development environments toward production. workItemId: the DevOps Center work item record ID
This record as markdown: /tools/io-github-semwalajay83-sem-salesforce-metadata-mcp/sf-devops-promote-work-item.md
What sf_devops_promote_work_item does on Salesforce Metadata Mcp
AI agents invoke sf_devops_promote_work_item 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.
Why sf_devops_promote_work_item is rated High
This tool triggers an external pipeline promotion operation, moving code/configuration changes through stages toward production. It doesn't just write data — it executes a workflow action with significant downstream effects, potentially deploying changes to production Salesforce environments. Misuse could result in unintended code or metadata being promoted to production, hence high severity.
From the tool's definition Promotes a DevOps Center work item to the next pipeline stage... progression of changes from development environments toward production
Attacks that exploit this kind of access
The rule that runs sf_devops_promote_work_item 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_devops_promote_work_item, this is the rule to start with:
sf_devops_promote_work_item 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Salesforce Metadata Mcp, apply this rule, and every sf_devops_promote_work_item call is checked against it from then on.
Questions about sf_devops_promote_work_item
Promotes a DevOps Center work item to the next pipeline stage. Moving work items through the pipeline represents the progression of changes from development environments toward production. workItemId: the DevOps Center work item record ID. 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.
Register the Salesforce Metadata MCP server in PolicyLayer and add a rule for sf_devops_promote_work_item: 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_devops_promote_work_item is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the sf_devops_promote_work_item 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_devops_promote_work_item. 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_devops_promote_work_item 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.
Across the catalogue