create_deal_pipeline
Create a Deal pipeline with ordered stages in the current workspace. Stages are created in the given order; the first is the default stage unless one sets is_default=true, and omitting stages creates the standard default stages. Returns the pipeline with its new stage ids.
This record as markdown: /tools/sankahq-sanka-mcp/create-deal-pipeline.md
What create_deal_pipeline does on Sanka MCP Server
AI agents use create_deal_pipeline to create or update resources in Sanka MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sanka MCP Server environment.
Why create_deal_pipeline is rated Medium
An AI agent can call create_deal_pipeline faster than any human can review: one bad instruction and it creates or modifies resources in Sanka MCP Server by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs create_deal_pipeline 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 create_deal_pipeline, this is the rule to start with:
create_deal_pipeline stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 create_deal_pipeline call is checked against it from then on.
Questions about create_deal_pipeline
Create a Deal pipeline with ordered stages in the current workspace. Stages are created in the given order; the first is the default stage unless one sets is_default=true, and omitting stages creates the standard default stages. Returns the pipeline with its new stage ids. It is categorised as a Write tool in the Sanka MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for create_deal_pipeline: 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.
create_deal_pipeline is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_deal_pipeline 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 create_deal_pipeline. 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.
create_deal_pipeline 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