AI agents call search_app_tags 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 |
|---|---|---|---|
sort | string | — | Sort direction. Valid values: asc, desc. Defaults to desc. |
search | string | — | Optional search keyword for fuzzy matching against tag names. |
current | number | — | Page number for pagination. Starts at 1. |
orderBy | string | — | Sort field. Valid values: tagName, id. Defaults to id. |
pageSize | number | — | Page size for pagination. Supports 1-100. Defaults to 10 when omitted. |
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 metadata (application tags) from the Yunxiao DevOps platform for query/discovery purposes. It has no side effects, does not execute commands, does not modify data, and does not trigger external operations. It is a pure Read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name contains 'search' and description states it 'Search[es] AppStack application tags' with no mention of modification, deletion, or execution.
Attacks that exploit this kind of access
Search AppStack application tags in a Yunxiao organization. Application tags are used to categorize and label applications for organizational purposes. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
search_app_tags accepts 6 parameters: sort, search, current, orderBy, pageSize, organizationId. 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 search_app_tags: 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.
search_app_tags 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 search_app_tags 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 search_app_tags. 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.
search_app_tags 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 →