pipedrive_list_organizations
List Pipedrive organizations (companies).
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/pipedrive-list-organizations.md
What pipedrive_list_organizations does on UnClick
AI agents call pipedrive_list_organizations 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 | — | Organizations to return (max 100, default 25) |
api_token | string | Yes | Pipedrive API token |
Parameters from the server's own tool schema.
Why pipedrive_list_organizations is rated Low
The 'list' operation is a read-only action that retrieves existing organization data from Pipedrive without creating, modifying, or deleting anything. This falls squarely within the Read category. The blast radius is minimal as it only exposes existing CRM data that the authenticated user already has access to. Low severity because listing is a standard query operation.
From the tool's definition Tool name 'pipedrive_list_organizations' and description 'List Pipedrive organizations (companies)' indicate a retrieval/query operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs pipedrive_list_organizations 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_organizations, this is the rule to start with:
pipedrive_list_organizations 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_organizations call is checked against it from then on.
Questions about pipedrive_list_organizations
List Pipedrive organizations (companies). It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
pipedrive_list_organizations 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_organizations: 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_organizations 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_organizations 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_organizations. 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_organizations 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