sf_commit_devops_work_item
Commits changes for a DevOps Center work item by creating a commit record associated with the work item. Records the commit message for audit tracking. workItemId: DevOps Center work item ID message: commit message describing the changes
This record as markdown: /tools/io-github-semwalajay83-sem-salesforce-metadata-mcp/sf-commit-devops-work-item.md
What sf_commit_devops_work_item does on Salesforce Metadata Mcp
AI agents use sf_commit_devops_work_item 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_commit_devops_work_item is rated Medium
This tool creates/modifies data (a commit record) in a reversible manner. While it affects version control and audit trails in Salesforce, the changes are not inherently destructive—commits can typically be rolled back or amended. It does not execute arbitrary code, delete data irreversibly, or move money.
From the tool's definition The tool 'commits changes' and 'creates a commit record' associated with a DevOps Center work item, modifying metadata and audit records in Salesforce.
Attacks that exploit this kind of access
The rule that runs sf_commit_devops_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_commit_devops_work_item, this is the rule to start with:
sf_commit_devops_work_item 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_commit_devops_work_item call is checked against it from then on.
Questions about sf_commit_devops_work_item
Commits changes for a DevOps Center work item by creating a commit record associated with the work item. Records the commit message for audit tracking. workItemId: DevOps Center work item ID message: commit message describing the changes. 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_commit_devops_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_commit_devops_work_item 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_commit_devops_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_commit_devops_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_commit_devops_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.
This server
Across the catalogue