get_deal_fields
AI agents call get_deal_fields to retrieve information from Pipedrive MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves deal field metadata/schema from Pipedrive CRM. It performs no modifications, deletions, or financial transactions. The empty description slightly reduces confidence, but the naming pattern and sibling context strongly suggest it queries field definitions. Read operations on CRM metadata pose minimal risk (low severity) to CRM systems.
From the tool's definition Tool name 'get_deal_fields' follows the 'get_*' pattern consistent with sibling tools like 'get_activities', 'get_deal', 'get_organization_fields', which are all retrieval operations.
Attacks that exploit this kind of access
get_deal_fields. It is categorised as a Read tool in the Pipedrive MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Pipedrive MCP Server MCP server in PolicyLayer and add a rule for get_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 Pipedrive MCP Server. Nothing to install.
get_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 get_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 get_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.
get_deal_fields is provided by the Pipedrive MCP Server MCP server (osherai/pipedrive-mcp-python). 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 →