Low Risk

sf_won_revenue_by_campaign

Aggregate Closed Won Opportunity revenue grouped by primary Campaign (CampaignId on the Opportunity). Returns campaign name, count of won deals, and total won revenue. Filter by close date range. Answers 'which campaigns actually drove closed revenue?'

Part of the Salesforce Marketing MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call sf_won_revenue_by_campaign to retrieve information from Salesforce Marketing without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though sf_won_revenue_by_campaign only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

salesforce-marketing.yaml
tools:
  sf_won_revenue_by_campaign:
    rules:
      - action: allow

See the full Salesforce Marketing policy for all 47 tools.

Tool Name sf_won_revenue_by_campaign
Category Read
Risk Level Low

View all 47 tools →

Agents calling read-class tools like sf_won_revenue_by_campaign have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the sf_won_revenue_by_campaign tool do? +

Aggregate Closed Won Opportunity revenue grouped by primary Campaign (CampaignId on the Opportunity). Returns campaign name, count of won deals, and total won revenue. Filter by close date range. Answers 'which campaigns actually drove closed revenue?'. It is categorised as a Read tool in the Salesforce Marketing MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on sf_won_revenue_by_campaign? +

Add a rule in your Intercept YAML policy under the tools section for sf_won_revenue_by_campaign. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Salesforce Marketing MCP server.

What risk level is sf_won_revenue_by_campaign? +

sf_won_revenue_by_campaign is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit sf_won_revenue_by_campaign? +

Yes. Add a rate_limit block to the sf_won_revenue_by_campaign rule in your Intercept 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.

How do I block sf_won_revenue_by_campaign completely? +

Set action: deny in the Intercept policy for sf_won_revenue_by_campaign. 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.

What MCP server provides sf_won_revenue_by_campaign? +

sf_won_revenue_by_campaign is provided by the Salesforce Marketing MCP server (salesforce-marketing-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.