AI agents call get_testcase_field_config 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. |
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 configuration metadata about test case fields in a repository. It is a passive query operation that returns information about available fields, similar to a schema inspection or introspection call. There is no data modification, deletion, code execution, or financial impact.
From the tool's definition Tool description states 'Get the field configuration' and 'understand available custom fields' — retrieval of metadata/schema information with no modification or execution of side effects.
Attacks that exploit this kind of access
Get the field configuration for test cases in a Projex testcase repository. Use this to understand available custom fields before creating or searching test cases. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
get_testcase_field_config accepts 2 parameters: testRepoId, 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 get_testcase_field_config: 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_field_config 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_field_config 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_field_config. 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_field_config 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 →