run_apex_tests · Salesforce CLI MCP Server MCP

WHAT IT DOES

What run_apex_tests does on Salesforce CLI MCP Server

AI agents invoke run_apex_tests to trigger actions in Salesforce CLI 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 IT NEEDS A POLICY

Why run_apex_tests needs a policy

This tool triggers execution of code (Apex tests) in an external system (Salesforce org) based on user-supplied arguments (test level, classes, suites). While tests are typically read-only validation operations, the blast radius is high because: (1) tests can have side effects within the org (modify test data, trigger workflows, call external services), (2) a malicious or misconfigured test suite could corrupt…

From the tool's definition Tool executes Apex unit tests in a Salesforce organization via CLI, with options for test level, specific classes, suites, and code coverage collection.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_apex_tests Rate-limited

run_apex_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_apex_tests": {
      "limits": [
        {
          "counter": "run_apex_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 Salesforce CLI MCP Server, so you can run agents against it safely.

FAQ

Questions about run_apex_tests

What does the run_apex_tests tool do? +

Run Apex tests in a Salesforce Org from a project. This command allows you to execute unit tests with various options including test level, specific classes, suites, and code coverage collection. Tests can be run synchronously or asynchronously. Use this to validate your Apex code and ensure proper test coverage. It is categorised as a Execute tool in the Salesforce CLI MCP Server 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_apex_tests? +

Register the Salesforce CLI MCP Server MCP server in PolicyLayer and add a rule for run_apex_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 Salesforce CLI MCP Server. Nothing to install.

What risk level is run_apex_tests? +

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

Can I rate-limit run_apex_tests? +

Yes. Add a rate_limit block to the run_apex_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_apex_tests completely? +

Set action: deny in the PolicyLayer policy for run_apex_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_apex_tests? +

run_apex_tests is provided by the Salesforce CLI MCP Server MCP server (perrynet/salesforce-cli-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.