get_activities
AI agents call get_activities to retrieve information from Pipedrive MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool follows the 'get_*' naming convention used throughout the Pipedrive MCP Server for retrieval operations. No description is available, but context from sibling tools and the name strongly indicate this retrieves activity records from Pipedrive CRM without modification or side effects. Low confidence penalty applied due to empty description, but the evidence is sufficient to classify as Read.
From the tool's definition Tool name 'get_activities' with verb 'get' indicates data retrieval. Description is empty but sibling tools (get_activity_types, get_deal, get_deals, get_person, etc.) are all Read operations, establishing a consistent pattern of query-only tools on this…
Attacks that exploit this kind of access
get_activities. It is categorised as a Read tool in the Pipedrive MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Pipedrive MCP Server MCP server in PolicyLayer and add a rule for get_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 Pipedrive MCP Server. Nothing to install.
get_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_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_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_activities is provided by the Pipedrive MCP Server MCP server (osherai/pipedrive-mcp-python). 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 →