Search Salesforce leads by name, email, or company using SOSL full-text search. Returns matching leads with Id, name, email, company, title, status, and lead source. Use this for fuzzy lookups; use sf_lead_by_email for exact email matches.
AI agents call sf_search_leads 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 |
|---|---|---|---|
q | string | Yes | Search query (name, email, or company) |
limit | integer | — |
Parameters from the server's own tool schema.
This tool performs a SOSL full-text search query to retrieve lead records matching specified criteria. It has no side effects—it does not create, modify, delete, or execute any operations. The fuzzy lookup functionality is purely informational. This is a classic Read operation that queries and returns data without altering state.
From the tool's definition Tool description states 'Search Salesforce leads' and 'Returns matching leads with Id, name, email, company, title, status, and lead source.' The verb 'Search' and 'Returns' indicate retrieval only with no modification capability.
Attacks that exploit this kind of access
Search Salesforce leads by name, email, or company using SOSL full-text search. Returns matching leads with Id, name, email, company, title, status, and lead source. Use this for fuzzy lookups; use sf_lead_by_email for exact email matches. It is categorised as a Read tool in the Salesforce Marketing MCP Server, which means it retrieves data without modifying state.
sf_search_leads accepts 2 parameters: q, limit. Required: q. 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_search_leads: 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_search_leads 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_search_leads 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_search_leads. 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_search_leads 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 →