AI agents call list_testcase_repositories 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. |
perPage | number | — | Page size for pagination. Supports 1-100. Defaults to 100 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 queries and retrieves a list of testcase repositories from a Yunxiao organization. It performs a read-only operation without creating, modifying, deleting, or executing any code. The blast radius of misuse is minimal—an agent would gain visibility into test repositories but cannot alter infrastructure or trigger deployments.
From the tool's definition Tool name 'list_testcase_repositories' with verb 'list' and description states it 'List Projex testcase repositories' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List Projex testcase repositories in a Yunxiao organization. A testcase repository is a container for organizing test cases. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
list_testcase_repositories accepts 3 parameters: page, perPage, 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 list_testcase_repositories: 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_testcase_repositories 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_testcase_repositories 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_testcase_repositories. 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_testcase_repositories 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 →