execute_unit_tests · Iris Execute MCP: Risk & Policy

WHAT IT DOES

What execute_unit_tests does on Iris Execute

AI agents invoke execute_unit_tests to trigger actions in Iris Execute. 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 IT NEEDS A POLICY

Why execute_unit_tests needs a policy

Unit test execution runs arbitrary test code against a system, which can have side effects depending on what the tests do (database modifications, API calls, external system interactions). While tests are typically intended to be read-only validations, they execute code and their effects depend on test implementation.

From the tool's definition Tool name 'execute_unit_tests' paired with server description mentioning 'unit testing with a fast DirectTestRunner' and sibling tools like 'execute_command' and 'execute_classmethod' that clearly execute code.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_unit_tests Rate-limited

execute_unit_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "execute_unit_tests": {
      "limits": [
        {
          "counter": "execute_unit_tests_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Iris Execute, so you can run agents against it safely.

FAQ

Questions about execute_unit_tests

What does the execute_unit_tests tool do? +

execute_unit_tests. It is categorised as a Execute tool in the Iris Execute MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on execute_unit_tests? +

Register the Iris Execute MCP server in PolicyLayer and add a rule for execute_unit_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 Iris Execute. Nothing to install.

What risk level is execute_unit_tests? +

execute_unit_tests is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit execute_unit_tests? +

Yes. Add a rate_limit block to the execute_unit_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.

How do I block execute_unit_tests completely? +

Set action: deny in the PolicyLayer policy for execute_unit_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.

What MCP server provides execute_unit_tests? +

execute_unit_tests is provided by the Iris Execute MCP server (jbrandtmse/iris-execute-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.