pipedrive_get_person
Get detailed information about a specific person by ID.
This record as markdown: /tools/ckalima-pipedrive-mcp-server/pipedrive-get-person.md
What pipedrive_get_person does on Pipedrive MCP Server
AI agents call pipedrive_get_person to retrieve information from Pipedrive MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why pipedrive_get_person is rated Low
This tool retrieves contact/person information from Pipedrive CRM by ID lookup. It performs a query operation with no side effects, no data modification, no code execution, and no destructive actions. The severity is low because unauthorized access to contact information, while a privacy concern, has limited immediate blast radius compared to tools that modify or delete data.
From the tool's definition Tool name 'pipedrive_get_person' and description 'Get detailed information about a specific person by ID' explicitly retrieve data without modification.
Attacks that exploit this kind of access
The rule that runs pipedrive_get_person safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Pipedrive MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pipedrive_get_person, this is the rule to start with:
pipedrive_get_person is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Pipedrive MCP Server, apply this rule, and every pipedrive_get_person call is checked against it from then on.
Questions about pipedrive_get_person
Get detailed information about a specific person by ID. 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 pipedrive_get_person: 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.
pipedrive_get_person 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 pipedrive_get_person 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 pipedrive_get_person. 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.
pipedrive_get_person is provided by the Pipedrive MCP Server MCP server (ckalima/pipedrive-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Pipedrive MCP Server, and thousands of servers like it.
This server
Across the catalogue