List stages of a pipeline (default: Renda Fixa, id=6). Returns stage_ids for move_deal_to_stage.
AI agents call list_stages to retrieve information from Mcp Pipedrive without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves existing pipeline stage data without creating, modifying, deleting, or executing any operations. It serves as a lookup function to obtain stage_ids needed by other tools. The blast radius is minimal as misuse would only expose stage enumeration information, which is non-sensitive metadata in a CRM context.
From the tool's definition Tool description states 'List stages of a pipeline' - the verb 'List' and the read-only nature of retrieving pipeline stage information with no mention of modification, deletion, or side effects.
Attacks that exploit this kind of access
List stages of a pipeline (default: Renda Fixa, id=6). Returns stage_ids for move_deal_to_stage. It is categorised as a Read tool in the Mcp Pipedrive MCP Server, which means it retrieves data without modifying state.
Register the Mcp Pipedrive MCP server in PolicyLayer and add a rule for list_stages: 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.
list_stages 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 list_stages 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 list_stages. 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.
list_stages 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 →