list_deal_pipelines
Discover the deal pipelines and stages defined in the current workspace. Use this when the user wants to understand pipeline structure, list available stages, or describe deal positions in context.
This record as markdown: /tools/sankahq-sanka-mcp/list-deal-pipelines.md
What list_deal_pipelines does on Sanka MCP Server
AI agents call list_deal_pipelines to retrieve information from Sanka 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 list_deal_pipelines is rated Low
This tool retrieves and lists metadata about deal pipeline structures and stages. It performs no modifications, deletions, code execution, or financial transactions. The action is read-only information gathering, fitting the 'Read' category. Severity is low because discovering pipeline structure poses minimal risk even if an AI agent calls it unnecessarily.
From the tool's definition Tool name 'list_deal_pipelines' and description explicitly states it 'Discover the deal pipelines and stages defined in the current workspace' and 'list available stages' — pure retrieval/query operations with no side effects.
Attacks that exploit this kind of access
The rule that runs list_deal_pipelines safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sanka MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_deal_pipelines, this is the rule to start with:
list_deal_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 Sanka MCP Server, apply this rule, and every list_deal_pipelines call is checked against it from then on.
Questions about list_deal_pipelines
Discover the deal pipelines and stages defined in the current workspace. Use this when the user wants to understand pipeline structure, list available stages, or describe deal positions in context. It is categorised as a Read tool in the Sanka MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for list_deal_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 Sanka MCP Server. Nothing to install.
list_deal_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 list_deal_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 list_deal_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.
list_deal_pipelines is provided by the Sanka MCP Server MCP server (sankahq/sanka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sanka MCP Server, and thousands of servers like it.
This server
Across the catalogue