search_deals
AI agents call search_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.
Although the description is empty, the tool name and server context strongly suggest this retrieves or queries deal data from Pipedrive CRM. The naming convention aligns with other Read category tools on this server. Medium severity is assigned because misuse could expose sensitive business deal information (customer data, pricing, pipeline status) but cannot directly modify or delete data.
From the tool's definition Tool name 'search_deals' follows the pattern of sibling read-only tools like 'get_deals', 'get_deal', and 'get_deal_notes'. The verb 'search' indicates query/retrieval operations without modification or deletion.
Attacks that exploit this kind of access
search_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 search_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.
search_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 search_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 search_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.
search_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 →