sf_detect_devops_merge_conflict

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-detect-devops-merge-conflict.md

WHAT IT DOES

What sf_detect_devops_merge_conflict does on Salesforce Metadata Mcp

AI agents call sf_detect_devops_merge_conflict 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_detect_devops_merge_conflict is rated Low

This tool queries DevOps Center to retrieve merge conflict information associated with a work item. It performs a diagnostic check with no side effects—it does not create, modify, execute, delete, or commit any changes. It is purely informational, designed to help users assess the state of a work item before taking action elsewhere.

From the tool's definition The tool description uses "Checks" and "Returns", which are read-only operations. It examines a work item for merge conflicts and returns details without modifying, executing, or deleting anything.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

sf_detect_devops_merge_conflict Allowed

sf_detect_devops_merge_conflict 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_detect_devops_merge_conflict": {}
  }
}

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

FAQ

Questions about sf_detect_devops_merge_conflict

What does the sf_detect_devops_merge_conflict tool do? +

Checks a DevOps Center work item for merge conflicts. Returns the work item details and any associated merge conflict records. Use before promoting a work item to identify conflicts that need resolution. workItemId: DevOps Center work item ID. 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_detect_devops_merge_conflict? +

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

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

Can I rate-limit sf_detect_devops_merge_conflict? +

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

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

sf_detect_devops_merge_conflict 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

detect_slop on Slop Cop → The MCP Attack Database →

Guides

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