sf_retrieve_metadata
Retrieves metadata components from the org by initiating a SOAP retrieve operation. Returns an async job ID. The org will package the requested components — use this to read existing configuration before making changes, back up metadata, or understand the current state of a setup item. Returns th...
This record as markdown: /tools/io-github-semwalajay83-sem-salesforce-metadata-mcp/sf-retrieve-metadata.md
What sf_retrieve_metadata does on Salesforce Metadata Mcp
AI agents call sf_retrieve_metadata 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_retrieve_metadata is rated Low
This tool performs a read-only query of Salesforce metadata. It retrieves existing configuration state without creating, modifying, deleting, or executing any changes. The stated use cases (read existing configuration before making changes, back up metadata, understand current state) all indicate non-destructive information retrieval.
From the tool's definition Tool description explicitly states it 'Retrieves metadata components' and is used to 'read existing configuration' and 'back up metadata' or 'understand the current state'.
Attacks that exploit this kind of access
The rule that runs sf_retrieve_metadata 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_retrieve_metadata, this is the rule to start with:
sf_retrieve_metadata 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_retrieve_metadata call is checked against it from then on.
Questions about sf_retrieve_metadata
Retrieves metadata components from the org by initiating a SOAP retrieve operation. Returns an async job ID. The org will package the requested components — use this to read existing configuration before making changes, back up metadata, or understand the current state of a setup item. Returns the retrieve request ID; the actual zip is available via Metadata API checkRetrieveStatus. 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_retrieve_metadata: 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_retrieve_metadata 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_retrieve_metadata 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_retrieve_metadata. 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_retrieve_metadata 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