pipedrive_list_phases
List all phases for a project board. board_id is required. Returns the complete list (no pagination — the phases endpoint returns all records for a board at once). (Projects add-on; Projects API in public beta.)
This record as markdown: /tools/ckalima-pipedrive-mcp-server/pipedrive-list-phases.md
What pipedrive_list_phases does on Pipedrive MCP Server
AI agents call pipedrive_list_phases 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_list_phases is rated Low
This tool retrieves and queries phase data from a Pipedrive project board using a required board_id parameter. It has no side effects and does not modify, create, or delete any data. It is a straightforward read operation that fits the 'Read' category.
From the tool's definition Tool name 'pipedrive_list_phases' and description 'List all phases for a project board' indicate a retrieval operation with no modification or side effects.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs pipedrive_list_phases 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_list_phases, this is the rule to start with:
pipedrive_list_phases 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_list_phases call is checked against it from then on.
Questions about pipedrive_list_phases
List all phases for a project board. board_id is required. Returns the complete list (no pagination — the phases endpoint returns all records for a board at once). (Projects add-on; Projects API in public beta.). 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_list_phases: 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_list_phases 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_phases 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_phases. 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_phases 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