Clear (set to null) one custom field on a deal. Auto-backed up.
AI agents use clear_deal_custom_field to create or update resources in Mcp Pipedrive — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Pipedrive environment.
This tool sets a custom field to null, which is a modification of existing data. Although it clears data, the 'Auto-backed up' note indicates it is reversible via restore, placing it in the Write category rather than Destructive. The blast radius is medium as it affects individual deal fields and can be restored.
From the tool's definition Clear (set to null) one custom field on a deal. Auto-backed up.
Attacks that exploit this kind of access
Clear (set to null) one custom field on a deal. Auto-backed up. It is categorised as a Write tool in the Mcp Pipedrive MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Pipedrive MCP server in PolicyLayer and add a rule for clear_deal_custom_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.
clear_deal_custom_field is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the clear_deal_custom_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 clear_deal_custom_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.
clear_deal_custom_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 →