sf_list_devops_projects
Lists all DevOps Center projects in the org. Returns project names, IDs, and associated pipeline information. Use to discover project IDs needed for other DevOps Center operations.
This record as markdown: /tools/io-github-semwalajay83-sem-salesforce-metadata-mcp/sf-list-devops-projects.md
What sf_list_devops_projects does on Salesforce Metadata Mcp
AI agents call sf_list_devops_projects 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.
Why sf_list_devops_projects is rated Low
This tool retrieves and queries existing DevOps Center project metadata without creating, modifying, deleting, or executing any operations. It is purely informational, used for discovery purposes. The low severity reflects minimal blast radius—an agent listing projects cannot cause harm beyond information disclosure of project identifiers that are typically known within the organization.
From the tool's definition Tool performs a 'Lists all DevOps Center projects' operation that 'Returns project names, IDs, and associated pipeline information' with explicit intent to 'discover project IDs needed for other DevOps Center operations.' The verb 'lists' and return of…
Attacks that exploit this kind of access
The rule that runs sf_list_devops_projects 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_list_devops_projects, this is the rule to start with:
sf_list_devops_projects is read-only, so it stays allowed. 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_list_devops_projects call is checked against it from then on.
Questions about sf_list_devops_projects
Lists all DevOps Center projects in the org. Returns project names, IDs, and associated pipeline information. Use to discover project IDs needed for other DevOps Center operations. It is categorised as a Read tool in the Salesforce Metadata Mcp MCP Server, which means it retrieves data without modifying state.
Register the Salesforce Metadata MCP server in PolicyLayer and add a rule for sf_list_devops_projects: 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_list_devops_projects is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the sf_list_devops_projects 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_list_devops_projects. 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_list_devops_projects 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