Set org_id on a deal. Auto-backed up.
AI agents use link_organization_to_deal to create or update resources in Mcp Pipedrive — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Pipedrive environment.
This tool modifies existing deal records by setting an organization relationship, making it a Write operation. While auto-backup is mentioned, this does not prevent the modification itself. The blast radius is medium: incorrect organization linking could corrupt CRM pipeline data and require manual correction, but the change is reversible (can be unlinked). Not Destructive because the action is not irreversible.
From the tool's definition 'Set org_id on a deal. Auto-backed up.' — the tool modifies deal data by linking an organization to it, creating a relationship that can be reversed.
Attacks that exploit this kind of access
Set org_id on a deal. Auto-backed up. It is categorised as a Write tool in the Mcp Pipedrive MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Pipedrive MCP server in PolicyLayer and add a rule for link_organization_to_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 Mcp Pipedrive. Nothing to install.
link_organization_to_deal is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the link_organization_to_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 link_organization_to_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.
link_organization_to_deal 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 →