运行 YAPI 自动化测试
AI agents invoke yapi_run_auto_test to trigger actions in YAPI MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Running automated tests is an Execute action because it triggers code execution and operations against external API systems. The blast radius is high if an AI agent misconfigures tests or targets wrong APIs, potentially causing unintended side effects on dependent systems, though it stops short of Destructive (no data deletion) or Financial (no money movement).
From the tool's definition Tool name 'yapi_run_auto_test' and description '运行 YAPI 自动化测试' (Run YAPI automated test) indicate execution of automated tests. This triggers external operations whose effects depend on test configuration and target APIs being tested.
Attacks that exploit this kind of access
运行 YAPI 自动化测试. It is categorised as a Execute tool in the YAPI MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the YAPI MCP Server MCP server in PolicyLayer and add a rule for yapi_run_auto_test: 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 YAPI MCP Server. Nothing to install.
yapi_run_auto_test is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the yapi_run_auto_test 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 yapi_run_auto_test. 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.
yapi_run_auto_test is provided by the YAPI MCP Server MCP server (zhhbinn/yapi-mcp). 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 →