Retrieve a complete Salesforce Contact record by its 18-character ID. Returns all standard fields including name, email, phone, title, account name, lead source, owner, and creation date.
AI agents call sf_get_contact 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 |
|---|---|---|---|
id | string | Yes | Salesforce Contact ID |
Parameters from the server's own tool schema.
This tool queries and retrieves existing contact data from Salesforce by ID. It performs no modifications, deletions, executions, or financial operations. The blast radius of misuse is limited to potential exposure of contact information, which is a read-level sensitivity concern. Classification as Read is appropriate.
From the tool's definition Tool name 'sf_get_contact' and description 'Retrieve a complete Salesforce Contact record by its 18-character ID. Returns all standard fields...' — uses 'Retrieve' and 'Returns', indicating data query with no modification or side effects.
Attacks that exploit this kind of access
Retrieve a complete Salesforce Contact record by its 18-character ID. Returns all standard fields including name, email, phone, title, account name, lead source, owner, and creation date. It is categorised as a Read tool in the Salesforce Marketing MCP Server, which means it retrieves data without modifying state.
sf_get_contact accepts 1 parameter: id. Required: id. 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_get_contact: 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_get_contact 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_get_contact 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_get_contact. 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_get_contact 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 →