sf_create_push_topic
Creates a Streaming API PushTopic for real-time record change notifications via the SObject API. Clients subscribe to /topic/TopicName using the CometD protocol. Specify the SOQL query that filters which records trigger events, and configure which operations (create, update, delete, undelete) and...
This record as markdown: /tools/io-github-semwalajay83-sem-salesforce-metadata-mcp/sf-create-push-topic.md
What sf_create_push_topic does on Salesforce Metadata Mcp
AI agents use sf_create_push_topic 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_create_push_topic is rated Medium
This tool creates a new PushTopic resource in Salesforce, which is a persistent configuration object that modifies system behavior. Once created, it remains in place and enables real-time event streaming based on SOQL filters—a reversible but consequential change to system infrastructure. It does not delete, execute arbitrary code, or move money, placing it in the Write category.
From the tool's definition Creates a Streaming API PushTopic for real-time record change notifications; tool name includes 'create'; description specifies 'Creates' and involves configuring operational parameters that persist in Salesforce metadata.
Attacks that exploit this kind of access
The rule that runs sf_create_push_topic 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_create_push_topic, this is the rule to start with:
sf_create_push_topic 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_create_push_topic call is checked against it from then on.
Questions about sf_create_push_topic
Creates a Streaming API PushTopic for real-time record change notifications via the SObject API. Clients subscribe to /topic/TopicName using the CometD protocol. Specify the SOQL query that filters which records trigger events, and configure which operations (create, update, delete, undelete) and fields trigger notifications. 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_create_push_topic: 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_create_push_topic 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_create_push_topic 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_create_push_topic. 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_create_push_topic 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