unity_testing_run_tests
Start a Unity Test Runner test run. Returns a job ID immediately — use unity_testing_get_job to poll for progress and results.
This record as markdown: /tools/anklebreaker-studio-unity-mcp-server/unity-testing-run-tests.md
What unity_testing_run_tests does on Unity MCP Server
AI agents invoke unity_testing_run_tests to trigger actions in Unity 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.
Why unity_testing_run_tests is rated High
This tool executes test suites within a Unity project, which can have unpredictable side effects depending on test implementation (e.g., tests may modify project state, write files, invoke external systems). While tests are typically intended to be side-effect-free, they execute arbitrary code within the Unity environment.
From the tool's definition Tool name contains 'run_tests' and description states 'Start a Unity Test Runner test run', indicating execution of code/tests with side effects dependent on test content and project state.
Attacks that exploit this kind of access
The rule that runs unity_testing_run_tests safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Unity MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For unity_testing_run_tests, this is the rule to start with:
unity_testing_run_tests stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Unity MCP Server, apply this rule, and every unity_testing_run_tests call is checked against it from then on.
Questions about unity_testing_run_tests
Start a Unity Test Runner test run. Returns a job ID immediately — use unity_testing_get_job to poll for progress and results. It is categorised as a Execute tool in the Unity MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Unity MCP Server MCP server in PolicyLayer and add a rule for unity_testing_run_tests: 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 Unity MCP Server. Nothing to install.
unity_testing_run_tests 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 unity_testing_run_tests 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 unity_testing_run_tests. 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.
unity_testing_run_tests is provided by the Unity MCP Server MCP server (anklebreaker-studio/unity-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Unity MCP Server, and thousands of servers like it.
Across the catalogue