crm_list_pipelines
List all pipelines and their stages in a CRM sub-account.
This record as markdown: /tools/io-github-0nork-0nmcp/crm-list-pipelines.md
What crm_list_pipelines does on 0nmcp
AI agents call crm_list_pipelines to retrieve information from 0nmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why crm_list_pipelines is rated Low
This tool queries and retrieves CRM pipeline data without creating, modifying, deleting, or executing any external operations. It is a straightforward read operation with minimal blast radius even if misused by an AI agent.
From the tool's definition Tool name 'crm_list_pipelines' with verb 'list' and description states 'List all pipelines' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs crm_list_pipelines safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 0nmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crm_list_pipelines, this is the rule to start with:
crm_list_pipelines 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 0nmcp, apply this rule, and every crm_list_pipelines call is checked against it from then on.
Questions about crm_list_pipelines
List all pipelines and their stages in a CRM sub-account. It is categorised as a Read tool in the 0nmcp MCP Server, which means it retrieves data without modifying state.
Register the 0n MCP server in PolicyLayer and add a rule for crm_list_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 0nmcp. Nothing to install.
crm_list_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 crm_list_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 crm_list_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.
crm_list_pipelines is provided by the 0n MCP server (0nmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 0n, and thousands of servers like it.
This server
Across the catalogue