sf_pipeline_by_lead_source

Summarize Opportunity pipeline grouped by Lead Source. Returns opportunity count, total amount, and weighted pipeline per source. Toggle openOnly and filter by date range. Use to understand which marketing channels are driving the most pipeline value.

Server Salesforce Marketing salesforce-marketing-mcp
Category Read
Risk class Low
Parameters 30 required

What sf_pipeline_by_lead_source does on Salesforce Marketing

AI agents call sf_pipeline_by_lead_source to retrieve information from Salesforce Marketing without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
dateTo string
dateFrom string
openOnly boolean

Parameters from the server's own tool schema.

Why sf_pipeline_by_lead_source needs a policy

This tool queries and summarizes existing Salesforce pipeline data grouped by lead source, returning metrics like opportunity count and pipeline value. It does not create, modify, delete, or execute arbitrary operations—it purely retrieves and aggregates data for reporting purposes. The 'openOnly' toggle and date range filter are parameters that refine the read query, not actions that change data.

From the tool's definition Tool name 'sf_pipeline_by_lead_source' and description 'Summarize Opportunity pipeline grouped by Lead Source.

Questions about sf_pipeline_by_lead_source

What does the sf_pipeline_by_lead_source tool do? +

Summarize Opportunity pipeline grouped by Lead Source. Returns opportunity count, total amount, and weighted pipeline per source. Toggle openOnly and filter by date range. Use to understand which marketing channels are driving the most pipeline value. It is categorised as a Read tool in the Salesforce Marketing MCP Server, which means it retrieves data without modifying state.

What parameters does sf_pipeline_by_lead_source accept? +

sf_pipeline_by_lead_source accepts 3 parameters: dateTo, dateFrom, openOnly. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on sf_pipeline_by_lead_source? +

Register the Salesforce Marketing MCP server in PolicyLayer and add a rule for sf_pipeline_by_lead_source: 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 Marketing. Nothing to install.

What risk level is sf_pipeline_by_lead_source? +

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

Can I rate-limit sf_pipeline_by_lead_source? +

Yes. Add a rate_limit block to the sf_pipeline_by_lead_source 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.

How do I block sf_pipeline_by_lead_source completely? +

Set action: deny in the PolicyLayer policy for sf_pipeline_by_lead_source. 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_pipeline_by_lead_source? +

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

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.