pipedrive_create_deal_field
Create a deal custom field. field_name and field_type are required. For enum/set types, options is required. The response data.field_code is the 40-char hash you must keep to update or delete the field later.
This record as markdown: /tools/ckalima-pipedrive-mcp-server/pipedrive-create-deal-field.md
What pipedrive_create_deal_field does on Pipedrive MCP Server
AI agents use pipedrive_create_deal_field 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_create_deal_field is rated Medium
This tool creates custom fields in the Pipedrive CRM system, which is a reversible Write operation. While it modifies the data schema rather than individual records, the creation is not destructive and can be undone. The severity is medium rather than high because custom field creation has limited blast radius - it affects configuration but not core business data like deals or contacts directly.
From the tool's definition Tool description states 'Create a deal custom field' which creates new data structures. The mention of 'field_code' for 'update or delete the field later' confirms this creates persistent custom field metadata that affects the CRM schema.
Attacks that exploit this kind of access
The rule that runs pipedrive_create_deal_field 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_create_deal_field, this is the rule to start with:
pipedrive_create_deal_field 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_create_deal_field call is checked against it from then on.
Questions about pipedrive_create_deal_field
Create a deal custom field. field_name and field_type are required. For enum/set types, options is required. The response data.field_code is the 40-char hash you must keep to update or delete the field later. 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_create_deal_field: 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_create_deal_field 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_create_deal_field 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_create_deal_field. 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_create_deal_field 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