get_deals
AI agents call get_deals 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.
The tool retrieves deal records from Pipedrive CRM. The name 'get_deals' (plural of 'get_deal') indicates a query/retrieval operation with no side effects. Despite the empty description, the naming pattern and context of sibling tools that are all simple data retrieval operations indicate this is a Read operation. Low severity because it only accesses existing data without modification or external effects.
From the tool's definition Tool name is 'get_deals' which follows standard REST/data retrieval naming convention. Sibling tools include 'get_activity', 'get_deal', 'get_organization' etc., all Read category tools for querying CRM data.
Attacks that exploit this kind of access
get_deals. 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_deals: 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_deals 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_deals 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_deals. 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_deals 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 →