AI agents use update-activity to create or update resources in Pipedrive MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pipedrive MCP Server environment.
This tool modifies existing activity records in a CRM system but does not delete data (which would be Destructive) or move money (Financial). The blast radius is medium because incorrect updates could corrupt customer activity records, affecting business processes and data integrity, but the change can be undone by subsequent updates.
From the tool's definition Tool name 'update-activity' and description 'Update an existing activity in Pipedrive' indicate modification of existing data. The server description confirms 'full CRUD access' with ability to 'manage...activities'.
Documented attack patterns abuse exactly the kind of access update-activity gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pipedrive MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for update-activity:
{
"version": "1",
"default": "deny",
"tools": {
"update-activity": {
"limits": [
{
"counter": "update-activity_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update-activity stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Update an existing activity in Pipedrive. It is categorised as a Write tool in the Pipedrive MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pipedrive MCP Server MCP server in PolicyLayer and add a rule for update-activity: 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.
update-activity is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update-activity 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 update-activity. 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.
update-activity is provided by the Pipedrive MCP Server MCP server (teapot-agency/mcp_pipedrive). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Pipedrive MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
39 Pipedrive MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.