pipedrive_add_deal_installment
Add an installment (payment schedule entry) to a deal. Growth+ plan required; the deal must have at least one one-time product and no recurring products.
This record as markdown: /tools/ckalima-pipedrive-mcp-server/pipedrive-add-deal-installment.md
What pipedrive_add_deal_installment does on Pipedrive MCP Server
AI agents use pipedrive_add_deal_installment 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.
Why pipedrive_add_deal_installment is rated Medium
This is a Write operation—it creates a new installment/payment schedule entry that modifies deal structure reversibly. While it touches financial data (payment schedules), it does not move money or create financial obligations; rather, it configures payment terms within Pipedrive.
From the tool's definition Tool adds/creates an installment payment schedule entry to a deal. Description states 'Add an installment' which is a create/write operation. The context indicates this modifies deal financial terms by establishing payment schedules.
Attacks that exploit this kind of access
The rule that runs pipedrive_add_deal_installment 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_add_deal_installment, this is the rule to start with:
pipedrive_add_deal_installment 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Pipedrive MCP Server, apply this rule, and every pipedrive_add_deal_installment call is checked against it from then on.
Questions about pipedrive_add_deal_installment
Add an installment (payment schedule entry) to a deal. Growth+ plan required; the deal must have at least one one-time product and no recurring products. 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 pipedrive_add_deal_installment: 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_add_deal_installment 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 pipedrive_add_deal_installment 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_add_deal_installment. 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_add_deal_installment 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