AI agents invoke swarm_run_test to trigger actions in Mcp Swarm. 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 test suites involves executing code whose behavior depends on test content and configuration. While tests are typically intended for validation rather than production changes, they execute arbitrary code that could have side effects (file I/O, network calls, environment modifications). This makes it Execute-category.
From the tool's definition Tool name 'swarm_run_test' and description '运行测试套件' (meaning 'run test suite') indicate execution of arbitrary test commands/scripts.
Attacks that exploit this kind of access
运行测试套件。. It is categorised as a Execute tool in the Mcp Swarm MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Swarm MCP server in PolicyLayer and add a rule for swarm_run_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 Mcp Swarm. Nothing to install.
swarm_run_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 swarm_run_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 swarm_run_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.
swarm_run_test is provided by the Mcp Swarm MCP server (moselu/mcp-swarm). 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 →