AI agents call get_testcase 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 |
|---|---|---|---|
testRepoId | string | Yes | Testcase repository ID (string). Use list_testcase_repositories to discover available repositories. |
testcaseId | string | Yes | Test case ID (string). Use search_testcases to discover valid 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 retrieves or queries test case data from a repository by ID lookup. There are no mentions of creation, modification, deletion, or execution of operations. The blast radius of misuse is minimal—an AI agent could only access existing test case data, which is informational. Classification as Read is appropriate.
From the tool's definition Tool description states 'Get a specific test case by ID' which is a retrieval operation with no side effects. The verb 'Get' and the action of fetching a testcase by ID indicates data query without modification.
Attacks that exploit this kind of access
Get a specific test case by ID from a Projex testcase repository. Use search_testcases to discover valid test case IDs. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
get_testcase accepts 3 parameters: testRepoId, testcaseId, organizationId. Required: testRepoId, testcaseId. 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 get_testcase: 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.
get_testcase 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 get_testcase 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 get_testcase. 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.
get_testcase 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 →