remove_deal_field
AI agents call remove_deal_field to permanently remove resources in Mcp Pipedrive — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool removes/deletes a deal field, which is an irreversible operation that cannot be undone without restore. This qualifies as Destructive rather than Write because field removal is not a reversible modification but a permanent deletion. The severity is high because it affects business-critical CRM data (Pipedrive deals), though the blast radius is limited to a single field rather than entire records.
From the tool's definition Tool name 'remove_deal_field' and server description stating it 'manage[s] Pipedrive deals...with automatic backup and restore capabilities' indicates irreversible deletion of deal field data.
Attacks that exploit this kind of access
remove_deal_field. It is categorised as a Destructive tool in the Mcp Pipedrive MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Pipedrive MCP server in PolicyLayer and add a rule for remove_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 Mcp Pipedrive. Nothing to install.
remove_deal_field is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_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 remove_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.
remove_deal_field is provided by the Mcp Pipedrive MCP server (leonardoceron-yvy/yvy-mcp-pipedrive). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →