Look up Salesforce Contact records by exact email address. Returns up to 10 matches with full contact details and associated account. Useful for deduplication checks before creating new contacts or for finding the Salesforce record for a known email.
AI agents call sf_contact_by_email 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 |
|---|---|---|---|
email | string | Yes | Email address to look up |
Parameters from the server's own tool schema.
This tool performs a read-only query operation against Salesforce Contact records. It retrieves and returns existing data without side effects or modifications. While it does expose contact details (PII), the risk is primarily information disclosure, which is inherent to read operations and falls within the low-severity Read category.
From the tool's definition Tool description states "Look up Salesforce Contact records by exact email address" and "Returns up to 10 matches with full contact details." The operations described are retrieval-only: "deduplication checks" and "finding the Salesforce record" — no…
Attacks that exploit this kind of access
Look up Salesforce Contact records by exact email address. Returns up to 10 matches with full contact details and associated account. Useful for deduplication checks before creating new contacts or for finding the Salesforce record for a known email. It is categorised as a Read tool in the Salesforce Marketing MCP Server, which means it retrieves data without modifying state.
sf_contact_by_email accepts 1 parameter: email. Required: email. 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_contact_by_email: 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_contact_by_email 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_contact_by_email 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_contact_by_email. 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_contact_by_email 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 →