pipedrive_get_project_changelog
Get the changelog for a project, showing what changed, when, and by whom. Returns paginated entries with actor_user_id, new_values, and old_values. (Projects add-on; Projects API in public beta.)
This record as markdown: /tools/ckalima-pipedrive-mcp-server/pipedrive-get-project-changelog.md
What pipedrive_get_project_changelog does on Pipedrive MCP Server
AI agents call pipedrive_get_project_changelog to retrieve information from Pipedrive MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why pipedrive_get_project_changelog is rated Low
This tool retrieves and queries existing audit/changelog data from Pipedrive's Projects module. It has no side effects, does not modify data, and presents no destructive or financial risk. The paginated read-only response confirms it is a passive data retrieval operation.
From the tool's definition Tool description states 'Get the changelog for a project' — a retrieval operation. Returns historical change log entries (actor_user_id, new_values, old_values) without modification.
Attacks that exploit this kind of access
The rule that runs pipedrive_get_project_changelog safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Pipedrive MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pipedrive_get_project_changelog, this is the rule to start with:
pipedrive_get_project_changelog is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Pipedrive MCP Server, apply this rule, and every pipedrive_get_project_changelog call is checked against it from then on.
Questions about pipedrive_get_project_changelog
Get the changelog for a project, showing what changed, when, and by whom. Returns paginated entries with actor_user_id, new_values, and old_values. (Projects add-on; Projects API in public beta.). 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 pipedrive_get_project_changelog: 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.
pipedrive_get_project_changelog 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 pipedrive_get_project_changelog 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 pipedrive_get_project_changelog. 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.
pipedrive_get_project_changelog is provided by the Pipedrive MCP Server MCP server (ckalima/pipedrive-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Pipedrive MCP Server, and thousands of servers like it.
This server
Across the catalogue