Track Marketing Qualified Lead (MQL) volume over time. Groups Lead records by creation date (week or month) where Status matches the target value (default: 'MQL'). Filter by date range. Use to spot MQL ramp-up, dips, or seasonal patterns in your lead pipeline.
AI agents call sf_mql_trend 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
dateTo | string | — | |
groupBy | string | Yes | |
dateFrom | string | — | |
statusValue | string | — |
Parameters from the server's own tool schema.
The tool performs historical analysis and reporting on Marketing Qualified Lead metrics by querying and grouping existing lead data. It retrieves information for trend analysis without creating, modifying, deleting, or executing external operations. This is a read-only reporting capability with minimal blast radius if misused—an agent could only retrieve or expose existing lead trend data.
From the tool's definition Tool description states it 'Track[s]' and 'Groups Lead records by creation date' where it 'Filter[s] by date range' to 'spot MQL ramp-up, dips, or seasonal patterns'.
Attacks that exploit this kind of access
Track Marketing Qualified Lead (MQL) volume over time. Groups Lead records by creation date (week or month) where Status matches the target value (default: 'MQL'). Filter by date range. Use to spot MQL ramp-up, dips, or seasonal patterns in your lead pipeline. It is categorised as a Read tool in the Salesforce Marketing MCP Server, which means it retrieves data without modifying state.
sf_mql_trend accepts 4 parameters: dateTo, groupBy, dateFrom, statusValue. Required: groupBy. The full parameter table on this page comes from the server's own tool schema.
Register the Salesforce Marketing MCP server in PolicyLayer and add a rule for sf_mql_trend: 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.
sf_mql_trend 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_mql_trend 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_mql_trend. 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_mql_trend 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.
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 →