delete-person

THE RISK

Critical Risk

Why delete-person needs a policy

This tool removes person records from the Pipedrive CRM. Although the description mentions '30-day recovery' (soft delete), the operation is explicitly labeled destructive and irreversibly deletes data from the system. Even with recovery windows, deletion operations that cannot be immediately undone fall under the Destructive category.

From the tool's definition Tool description explicitly states 'Delete a person' and includes CAUTION warning: 'This is a destructive operation.' The name 'delete-person' indicates irreversible data removal.

Documented attack patterns abuse exactly the kind of access delete-person gives an agent:

POLICY

How to control delete-person

PolicyLayer is an MCP gateway — it sits between your AI agents and Pipedrive MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete-person:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete-person"
  ]
}

delete-person disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Pipedrive MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Pipedrive MCP Server tools

Destructive delete-activity Delete an activity (soft delete with 30-day recovery). CAUTION: This is a destructive oper Destructive delete-deal Delete a deal (soft delete with 30-day recovery). CAUTION: This is a destructive operation Destructive delete-lead Delete a lead. CAUTION: This is a destructive operation. Destructive delete-note Delete a note. CAUTION: This is a destructive operation. Destructive delete-organization Delete an organization (soft delete with 30-day recovery). CAUTION: This is a destructive Write convert-lead-to-deal Convert a lead to a deal. Returns a conversion job ID for tracking status. Write create-activity Create a new activity (task, call, meeting, etc.) in Pipedrive Write create-deal Create a new deal in Pipedrive. All deals created through the API have origin=

All 39 Pipedrive MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Pipedrive MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete-person

What does the delete-person tool do? +

Delete a person (soft delete with 30-day recovery). CAUTION: This is a destructive operation. 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 delete-person? +

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

delete-person 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 delete-person? +

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

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

delete-person is provided by the Pipedrive MCP Server MCP server (teapot-agency/mcp_pipedrive). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Pipedrive MCP Server tool call.

Start from Pipedrive MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →