AI agents call get-deal 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 existing deal data from Pipedrive without creating, modifying, deleting, or executing any operations. It is a straightforward read operation that matches the 'Read' category definition: 'retrieves or queries data; no side effects (search, list, get, fetch)'. The low severity reflects minimal blast radius—misuse would only expose existing CRM data rather than cause destructive or financial harm.
From the tool's definition Tool name 'get-deal' and description 'Get a specific deal by ID' indicate data retrieval with no modification. The description explicitly states it retrieves a deal 'by ID including custom fields', which is a query operation with no side effects.
Documented attack patterns abuse exactly the kind of access get-deal gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pipedrive MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get-deal:
{
"version": "1",
"default": "deny",
"tools": {
"get-deal": {}
}
}get-deal is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get a specific deal by ID including custom 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: 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 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 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. 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 is provided by the Pipedrive MCP Server MCP server (teapot-agency/mcp_pipedrive). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Pipedrive MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
39 Pipedrive MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.