sf_check_deploy_status
Checks the status of an in-progress or recently completed metadata deployment by async job ID. Returns the status (Pending, InProgress, Succeeded, Failed, Canceled), component successes, failures, and test results. Use with the deploy ID returned from sf_deploy_metadata.
This record as markdown: /tools/io-github-semwalajay83-sem-salesforce-metadata-mcp/sf-check-deploy-status.md
What sf_check_deploy_status does on Salesforce Metadata Mcp
AI agents call sf_check_deploy_status 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_check_deploy_status is rated Low
sf_check_deploy_status retrieves and reports deployment status information without modifying, executing, or deleting anything. It is a read-only operation that queries the state of an existing deployment. The tool depends on a deploy ID provided by another tool (sf_deploy_metadata) and simply returns status data, making it a Read category operation with low risk.
From the tool's definition The tool "Checks the status of an in-progress or recently completed metadata deployment" and "Returns the status... component successes, failures, and test results." These are purely informational queries with no side effects.
Attacks that exploit this kind of access
The rule that runs sf_check_deploy_status 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_check_deploy_status, this is the rule to start with:
sf_check_deploy_status 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_check_deploy_status call is checked against it from then on.
Questions about sf_check_deploy_status
Checks the status of an in-progress or recently completed metadata deployment by async job ID. Returns the status (Pending, InProgress, Succeeded, Failed, Canceled), component successes, failures, and test results. Use with the deploy ID returned from sf_deploy_metadata. 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_check_deploy_status: 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_check_deploy_status 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_check_deploy_status 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_check_deploy_status. 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_check_deploy_status 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