Discover the ticket pipelines and stages defined in the current workspace. Use this before stage-based ticket updates so the stage keys match the workspace configuration.
AI agents call list_ticket_pipelines to retrieve information from Sanka MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only query operation that retrieves existing configuration data (ticket pipelines and stages) from the workspace. It has no capability to modify, delete, or execute operations. The primary purpose is to provide informational lookups needed for subsequent operations. The blast radius of misuse is minimal—an AI agent cannot cause harm by listing available pipelines.
From the tool's definition The tool name is 'list_ticket_pipelines' and the description states it 'Discover[s] the ticket pipelines and stages defined in the current workspace.' The verbs 'discover' and 'list' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Discover the ticket pipelines and stages defined in the current workspace. Use this before stage-based ticket updates so the stage keys match the workspace configuration. 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_ticket_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_ticket_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_ticket_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_ticket_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_ticket_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.
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 →