List all stages (statuses) of a specific pipeline (funnel), including their descriptions (tips). Use this to see what each stage means.
AI agents call get_pipeline_statuses to retrieve information from Kommo MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves pipeline stage metadata from the Kommo CRM system. It performs no modifications, deletions, or execution of external operations. The scope is limited to reading descriptive information about pipeline statuses, making it a straightforward Read operation with low risk if misused.
From the tool's definition Tool name and description both indicate retrieval-only behavior: 'List all stages (statuses)' and 'Use this to see what each stage means' demonstrate querying/fetching without modification or side effects.
Attacks that exploit this kind of access
List all stages (statuses) of a specific pipeline (funnel), including their descriptions (tips). Use this to see what each stage means. It is categorised as a Read tool in the Kommo MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Kommo MCP Server MCP server in PolicyLayer and add a rule for get_pipeline_statuses: 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 Kommo MCP Server. Nothing to install.
get_pipeline_statuses 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 get_pipeline_statuses 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 get_pipeline_statuses. 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.
get_pipeline_statuses is provided by the Kommo MCP Server MCP server (wdavidce/kommo-mcp-server). 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 →