sf_configure_change_data_capture
Enables Change Data Capture (CDC) for the specified Salesforce objects via the Metadata API. CDC publishes change events to the /data/ChangeEvents channel when records are created, updated, deleted, or undeleted. Provide an array of object API names to enable CDC on. Standard and custom objects a...
This record as markdown: /tools/io-github-semwalajay83-sem-salesforce-metadata-mcp/sf-configure-change-data-capture.md
What sf_configure_change_data_capture does on Salesforce Metadata Mcp
AI agents use sf_configure_change_data_capture 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.
Why sf_configure_change_data_capture is rated Medium
This tool modifies Salesforce org configuration by enabling CDC on objects, which is a reversible write operation. While it does not delete data or execute arbitrary code, it alters org-wide settings and enables event publishing, which could expose data changes to subscribers.
From the tool's definition Enables Change Data Capture (CDC) for specified Salesforce objects via the Metadata API. This modifies the configuration and enablement state of metadata settings on the org, which is a reversible configuration change.
Attacks that exploit this kind of access
The rule that runs sf_configure_change_data_capture 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_configure_change_data_capture, this is the rule to start with:
sf_configure_change_data_capture 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Salesforce Metadata Mcp, apply this rule, and every sf_configure_change_data_capture call is checked against it from then on.
Questions about sf_configure_change_data_capture
Enables Change Data Capture (CDC) for the specified Salesforce objects via the Metadata API. CDC publishes change events to the /data/ChangeEvents channel when records are created, updated, deleted, or undeleted. Provide an array of object API names to enable CDC on. Standard and custom objects are supported. 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.
Register the Salesforce Metadata MCP server in PolicyLayer and add a rule for sf_configure_change_data_capture: 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_configure_change_data_capture is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the sf_configure_change_data_capture 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_configure_change_data_capture. 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_configure_change_data_capture 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