AI agents call search_testcases 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: asc or desc. |
orderBy | string | — | Sort field: gmtCreate or name. |
perPage | number | — | Page size for pagination. Supports 1-100. Defaults to 100 when omitted. |
subject | string | — | Filter by testcase subject/title (contains match). |
conditions | string | — | Advanced conditions JSON string. Overrides simple filters. |
testRepoId | string | Yes | Testcase repository ID (string). Use list_testcase_repositories to discover available repositories. |
directoryId | string | — | Directory ID (string) to filter by. Use list_directories to discover directory IDs. |
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 performs a read-only search operation on test case data. It retrieves or queries existing test cases from a repository with no side effects, no code execution, no data modification, and no destructive operations. The blast radius of misuse is minimal—an agent could at worst enumerate or exfiltrate test case metadata, which is a low-severity information disclosure risk in a DevOps context.
From the tool's definition Tool name 'search_testcases' and description 'Search test cases within a single Projex testcase repository' indicates a query/search operation that retrieves data without modifying or deleting anything.
Attacks that exploit this kind of access
Search test cases within a single Projex testcase repository. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
search_testcases accepts 9 parameters: page, sort, orderBy, perPage, subject, conditions, testRepoId, directoryId, organizationId. Required: testRepoId. 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_testcases: 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_testcases 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_testcases 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_testcases. 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_testcases 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 →