run_tests · Squirex Dev MCP: Risk & Policy

WHAT IT DOES

What run_tests does on Squirex Dev

AI agents invoke run_tests to trigger actions in Squirex Dev. 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 run_tests needs a policy

This tool executes arbitrary Apex test code in a local environment using an interpreter. While test execution is typically safe in isolation, it runs code with side effects (database state changes, external API calls, file operations) that could be embedded in malicious tests. An AI agent could be tricked into executing adversarial tests that compromise the Salesforce instance or connected systems.

From the tool's definition Tool description explicitly states 'Execute Apex tests locally using the high-fidelity Go interpreter' and 'Returns structured test results with pass/fail status, assertion details, stack traces, and line-level code coverage.' The word 'Execute' combined with…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_tests Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_tests": {
      "limits": [
        {
          "counter": "run_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 Squirex Dev, so you can run agents against it safely.

FAQ

Questions about run_tests

What does the run_tests tool do? +

Execute Apex tests locally using the high-fidelity Go interpreter. Returns structured test results with pass/fail status, assertion details, stack traces, and line-level code coverage. It is categorised as a Execute tool in the Squirex Dev MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_tests? +

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

What risk level is run_tests? +

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

Can I rate-limit run_tests? +

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

How do I block run_tests completely? +

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

What MCP server provides run_tests? +

run_tests is provided by the Squirex Dev MCP server (squirex-dev/squirex-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.