pipedrive_update_product_field

Update a product custom field by field_code. Only field_name and ui_visibility can be changed (product fields have no description/important_fields/required_fields).

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-update-product-field.md

WHAT IT DOES

What pipedrive_update_product_field does on Pipedrive MCP Server

AI agents use pipedrive_update_product_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_update_product_field is rated Medium

This tool creates or modifies data reversibly by updating custom field configurations in Pipedrive. It does not delete data (ruling out Destructive), does not execute arbitrary code (ruling out Execute), and does not involve financial transactions (ruling out Financial).

From the tool's definition Tool name contains 'update' and description explicitly states it modifies product custom field properties ('Only field_name and ui_visibility can be changed'). The description indicates reversible modifications to metadata.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

pipedrive_update_product_field Rate-limited

pipedrive_update_product_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_update_product_field": {
      "limits": [
        {
          "counter": "pipedrive_update_product_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_update_product_field call is checked against it from then on.

FAQ

Questions about pipedrive_update_product_field

What does the pipedrive_update_product_field tool do? +

Update a product custom field by field_code. Only field_name and ui_visibility can be changed (product fields have no description/important_fields/required_fields). 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_update_product_field? +

Register the Pipedrive MCP Server MCP server in PolicyLayer and add a rule for pipedrive_update_product_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_update_product_field? +

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

Can I rate-limit pipedrive_update_product_field? +

Yes. Add a rate_limit block to the pipedrive_update_product_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_update_product_field completely? +

Set action: deny in the PolicyLayer policy for pipedrive_update_product_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_update_product_field? +

pipedrive_update_product_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

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

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