pipedrive_create_person_field

Create a person 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 to keep for later updates.

SERVERPipedrive MCP Server SOURCEckalima/pipedrive-mcp-server

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ckalima-pipedrive-mcp-server/pipedrive-create-person-field.md

WHAT IT DOES

What pipedrive_create_person_field does on Pipedrive MCP Server

AI agents use pipedrive_create_person_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.

RISK

Why pipedrive_create_person_field is rated Medium

This tool creates new custom field metadata in the Pipedrive CRM system, which is a reversible write operation. It does not delete, overwrite irreversibly, execute external code, or move money. The severity is medium because misconfiguration could create field naming conflicts or pollution of the CRM schema, but the impact is limited to schema organization rather than data loss or financial harm.

From the tool's definition Tool description states 'Create a person custom field' which is a data creation operation. The requirement for 'field_name and field_type' parameters, along with the instruction to 'keep for later updates' indicates this creates new structured data in…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs pipedrive_create_person_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_person_field, this is the rule to start with:

pipedrive_create_person_field Rate-limited

pipedrive_create_person_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pipedrive_create_person_field": {
      "limits": [
        {
          "counter": "pipedrive_create_person_field_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Pipedrive MCP Server, apply this rule, and every pipedrive_create_person_field call is checked against it from then on.

FAQ

Questions about pipedrive_create_person_field

What does the pipedrive_create_person_field tool do? +

Create a person 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 to keep for later updates. 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.

How do I enforce a policy on pipedrive_create_person_field? +

Register the Pipedrive MCP Server MCP server in PolicyLayer and add a rule for pipedrive_create_person_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.

What risk level is pipedrive_create_person_field? +

pipedrive_create_person_field is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit pipedrive_create_person_field? +

Yes. Add a rate_limit block to the pipedrive_create_person_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.

How do I block pipedrive_create_person_field completely? +

Set action: deny in the PolicyLayer policy for pipedrive_create_person_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.

What MCP server provides pipedrive_create_person_field? +

pipedrive_create_person_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.

KEEP EXPLORING

More on Pipedrive MCP Server, and thousands of servers like it.

This server

All 155 Pipedrive MCP Server tools →

Across the catalogue

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →