List all deal fields (default + custom) with their key (used in custom_fields dict) and field_type.
AI agents call list_deal_fields to retrieve information from Mcp Pipedrive without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only retrieval operation that queries Pipedrive's deal field metadata. It has no side effects, creates no data, executes no code, and does not delete or transfer funds. The information returned is metadata about field structure, not sensitive operational data, making it low-severity even if exposed.
From the tool's definition Tool name includes 'list' and description states it retrieves/lists 'all deal fields...with their key and field_type' without modifying any data.
Attacks that exploit this kind of access
List all deal fields (default + custom) with their key (used in custom_fields dict) and field_type. It is categorised as a Read tool in the Mcp Pipedrive MCP Server, which means it retrieves data without modifying state.
Register the Mcp Pipedrive MCP server in PolicyLayer and add a rule for list_deal_fields: 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.
list_deal_fields is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_deal_fields 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 list_deal_fields. 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.
list_deal_fields 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 →