AI agents call search_projects 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 |
|---|---|---|---|
name | string | — | Filter by project name (contains match). |
page | number | — | Page number for pagination. Starts at 1. |
sort | string | — | Sort direction: asc (ascending) or desc (descending). |
status | string | — | Comma-separated project status IDs. Use without filters to list all projects and inspect their statuses. |
creator | string | — | Comma-separated creator user IDs. Use list_project_members to find user IDs in the project. |
orderBy | string | — | Sort field, such as gmtCreate (creation time) or name. |
perPage | number | — | Page size for pagination. Most endpoints default to 20. |
conditions | string | — | Advanced filter conditions as a JSON string. Overrides simple filters when provided. |
organizationId | string | — | Yunxiao organization ID. When omitted, the server uses the user's default organization. |
extraConditions | string | — | Extra filter conditions as a JSON string, combined with conditions. |
Parameters from the server's own tool schema.
This tool retrieves and queries project metadata from the Yunxiao DevOps platform to help discover available projects. It has no capability to create, modify, delete, or execute operations—it is purely informational. The low severity reflects that discovering project IDs poses minimal risk; blast radius if misused by an AI agent would be limited to information disclosure about available projects in an organization.
From the tool's definition Tool description explicitly states 'Search Projex projects' and 'discover available projects'. The verb 'search' and the stated purpose of obtaining project IDs indicates data retrieval without modification or side effects.
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
Search Projex projects in a Yunxiao organization. Use this to discover available projects and obtain their project IDs before calling other project-scoped tools. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
search_projects accepts 10 parameters: name, page, sort, status, creator, orderBy, perPage, conditions, organizationId, extraConditions. 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_projects: 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_projects 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_projects 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_projects. 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_projects 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 →