AI agents call search_app_templates 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 |
|---|---|---|---|
page | number | — | Page number for pagination. Starts at 1. |
sort | string | — | Sort direction. Valid values: asc, desc. |
orderBy | string | — | Sort field. Valid values: id, gmtCreate. |
perPage | number | — | Page size for pagination. Supports 1-100. Defaults to 100 when omitted. |
nextToken | string | — | Keyset pagination token from the previous response. |
pagination | string | — | Pagination mode. Valid value: keyset. |
organizationId | string | — | Yunxiao organization ID. When omitted, the server uses the user's default organization. |
displayNameKeyword | string | — | Template display name keyword for filtering results. |
Parameters from the server's own tool schema.
This tool retrieves and queries application templates from the Yunxiao DevOps platform. It performs a search operation to discover available templates, which is a read-only action with no side effects, data modification, or execution capability. No data is created, deleted, or modified by this operation.
From the tool's definition Tool description states 'Search AppStack application templates' and 'discover templates before creating or deploying applications'. The verb 'search' and 'discover' indicate retrieval of information without modification or execution of side effects.
Attacks that exploit this kind of access
Search AppStack application templates. Use this to discover templates before creating or deploying applications. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
search_app_templates accepts 8 parameters: page, sort, orderBy, perPage, nextToken, pagination, organizationId, displayNameKeyword. 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_templates: 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_templates 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_templates 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_templates. 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_templates 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 →