AI agents call list_system_release_workflows to retrieve information from Yunxiao without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
systemName | string | Yes | System name. Use list_systems to discover valid names. |
organizationId | string | — | Yunxiao organization ID. When omitted, the server uses the user's default organization. |
Parameters from the server's own tool schema.
This tool retrieves and lists existing release workflows from the Yunxiao DevOps platform. It performs data discovery without side effects, side-stepping any infrastructure changes or code execution. The operation is informational in nature, consistent with the 'Read' category for retrieval operations.
From the tool's definition Tool description states 'List AppStack release workflows' - a read-only operation that retrieves/queries workflow data without modification. No delete, create, update, or execute keywords present.
Attacks that exploit this kind of access
List AppStack release workflows for a system. Use this after discovering a system via list_systems to find releases and their workflows. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
list_system_release_workflows accepts 2 parameters: systemName, organizationId. Required: systemName. The full parameter table on this page comes from the server's own tool schema.
Register the Yunxiao MCP server in PolicyLayer and add a rule for list_system_release_workflows: 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 Yunxiao. Nothing to install.
list_system_release_workflows 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_system_release_workflows 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_system_release_workflows. 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_system_release_workflows is provided by the Yunxiao MCP server (@futuretea/yunxiao-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 →