This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/pipedrive-list-persons.md
What pipedrive_list_persons does on UnClick
AI agents call pipedrive_list_persons to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Persons to return (max 100, default 25) |
api_token | string | Yes | Pipedrive API token |
Parameters from the server's own tool schema.
Why pipedrive_list_persons is rated Low
This tool queries and retrieves contact data from Pipedrive CRM without creating, modifying, or deleting records. It is a read-only operation with minimal blast radius if misused by an AI agent, as it only exposes existing contact information that the authorized user would already have access to. No financial, destructive, or side-effect operations are possible.
From the tool's definition Tool name contains 'list' and description states 'List Pipedrive persons (contacts)' — a straightforward data retrieval operation with no modification or deletion capability.
Attacks that exploit this kind of access
The rule that runs pipedrive_list_persons safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pipedrive_list_persons, this is the rule to start with:
pipedrive_list_persons 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 UnClick, apply this rule, and every pipedrive_list_persons call is checked against it from then on.
Questions about pipedrive_list_persons
List Pipedrive persons (contacts). It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
pipedrive_list_persons accepts 2 parameters: limit, api_token. Required: api_token. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for pipedrive_list_persons: 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 UnClick. Nothing to install.
pipedrive_list_persons 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_list_persons 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_list_persons. 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_list_persons is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue