List all pipelines (funnels) and their respective statuses (stages). Use this to understand the commercial structure.
AI agents call get_pipelines 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 and queries pipeline data from the Kommo CRM but produces no side effects, creates no data, executes no commands, and initiates no financial transactions. It is purely informational, allowing the AI to inspect the commercial structure of the CRM. Read operations have minimal blast radius—the worst outcome is information disclosure or a rate limit hit.
From the tool's definition Tool name 'get_pipelines' and description 'List all pipelines (funnels) and their respective statuses (stages)' indicate a retrieval operation. The verb 'List' and action of understanding structure without modification are hallmarks of a read-only query.
Attacks that exploit this kind of access
List all pipelines (funnels) and their respective statuses (stages). Use this to understand the commercial structure. 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_pipelines: 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_pipelines 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_pipelines 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_pipelines. 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_pipelines 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 →