List recent Task and Event records associated with a specific Contact. Returns subject, type, status, priority, due date, and description sorted by most recent. Use to review engagement history before account reviews, renewals, or re-engagement campaigns.
AI agents call sf_recent_activities_by_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 |
|---|---|---|---|
limit | integer | — | |
contactId | string | Yes |
Parameters from the server's own tool schema.
This tool queries and retrieves historical activity data associated with a contact. It performs no writes, deletions, executions, or financial operations. The worst-case misuse is information disclosure of non-sensitive engagement metadata (task subjects, statuses, dates), which represents minimal blast radius in a marketing context.
From the tool's definition Tool name 'sf_recent_activities_by_contact' and description states it 'List[s] recent Task and Event records' and 'Returns subject, type, status, priority, due date, and description' — purely retrieval operations with no modification, deletion, or side…
Attacks that exploit this kind of access
List recent Task and Event records associated with a specific Contact. Returns subject, type, status, priority, due date, and description sorted by most recent. Use to review engagement history before account reviews, renewals, or re-engagement campaigns. It is categorised as a Read tool in the Salesforce Marketing MCP Server, which means it retrieves data without modifying state.
sf_recent_activities_by_contact accepts 2 parameters: limit, contactId. Required: contactId. 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_recent_activities_by_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_recent_activities_by_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_recent_activities_by_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_recent_activities_by_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_recent_activities_by_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 →