pipedrive_delete_person_field_options

Bulk-delete options of a person enum/set field. Atomic: fails if any ID does not exist. Requires PIPEDRIVE_MODE=full (back-compat: PIPEDRIVE_ENABLE_DESTRUCTIVE=true).

SERVERPipedrive MCP Server SOURCEckalima/pipedrive-mcp-server

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What pipedrive_delete_person_field_options does on Pipedrive MCP Server

AI agents call pipedrive_delete_person_field_options to permanently remove resources in Pipedrive MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why pipedrive_delete_person_field_options is rated Critical

This tool irreversibly deletes field options from person enum/set fields in bulk. Deletion of data that cannot be undone is destructive. The requirement for explicit destructive mode enablement and atomic transaction semantics confirms this is a high-severity destructive operation that could impact data integrity and business workflows if invoked incorrectly by an AI agent.

From the tool's definition Tool name contains 'delete', description explicitly states 'Bulk-delete options' and 'Atomic: fails if any ID does not exist', requiring PIPEDRIVE_MODE=full or PIPEDRIVE_ENABLE_DESTRUCTIVE=true flag.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

pipedrive_delete_person_field_options Hidden

pipedrive_delete_person_field_options is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "pipedrive_delete_person_field_options"
  ]
}

RESTRICT 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_delete_person_field_options call is checked against it from then on.

FAQ

Questions about pipedrive_delete_person_field_options

What does the pipedrive_delete_person_field_options tool do? +

Bulk-delete options of a person enum/set field. Atomic: fails if any ID does not exist. Requires PIPEDRIVE_MODE=full (back-compat: PIPEDRIVE_ENABLE_DESTRUCTIVE=true). It is categorised as a Destructive tool in the Pipedrive MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on pipedrive_delete_person_field_options? +

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

pipedrive_delete_person_field_options is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit pipedrive_delete_person_field_options? +

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

Set action: deny in the PolicyLayer policy for pipedrive_delete_person_field_options. 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_delete_person_field_options? +

pipedrive_delete_person_field_options 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 → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →