sf_checkout_devops_work_item

Checks out a DevOps Center work item, moving it to

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-checkout-devops-work-item.md

WHAT IT DOES

What sf_checkout_devops_work_item does on Salesforce Metadata Mcp

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

RISK

Why sf_checkout_devops_work_item is rated Medium

The tool performs a checkout operation, which transitions a work item to a different state (from available to checked-out). This is a reversible modification of data—the work item can be checked back in or reassigned. It does not delete, execute arbitrary code, or move money, making it a Write action.

From the tool's definition Tool name 'sf_checkout_devops_work_item' and description 'Checks out a DevOps Center work item, moving it to' indicates a state-change operation that modifies work item status/assignment within Salesforce DevOps Center.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

sf_checkout_devops_work_item Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sf_checkout_devops_work_item": {
      "limits": [
        {
          "counter": "sf_checkout_devops_work_item_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_checkout_devops_work_item call is checked against it from then on.

FAQ

Questions about sf_checkout_devops_work_item

What does the sf_checkout_devops_work_item tool do? +

Checks out a DevOps Center work item, moving it to. 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_checkout_devops_work_item? +

Register the Salesforce Metadata MCP server in PolicyLayer and add a rule for sf_checkout_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.

What risk level is sf_checkout_devops_work_item? +

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

Can I rate-limit sf_checkout_devops_work_item? +

Yes. Add a rate_limit block to the sf_checkout_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.

How do I block sf_checkout_devops_work_item completely? +

Set action: deny in the PolicyLayer policy for sf_checkout_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.

What MCP server provides sf_checkout_devops_work_item? +

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

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 →