Get recent activities (events and tasks) for a specific contact
AI agents call get_contact_activities to retrieve information from Mcp Salesforce without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical activity data (events and tasks) for a contact without creating, modifying, or deleting any data. It has no side effects and presents minimal security risk. Even if an AI agent calls this tool with any contact identifier, the worst outcome is unauthorized data exposure of that contact's activity history, which is a read-level risk.
From the tool's definition Tool description states "Get recent activities" which is a retrieval operation with no modification capability. The verb 'Get' indicates a query/fetch operation.
Attacks that exploit this kind of access
Get recent activities (events and tasks) for a specific contact. It is categorised as a Read tool in the Mcp Salesforce MCP Server, which means it retrieves data without modifying state.
Register the Mcp Salesforce MCP server in PolicyLayer and add a rule for get_contact_activities: 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 Mcp Salesforce. Nothing to install.
get_contact_activities 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 get_contact_activities 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 get_contact_activities. 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.
get_contact_activities is provided by the Mcp Salesforce MCP server (@snokam/mcp-salesforce). 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 →