sf_apex_test_run · Salesforce CLI MCP Server MCP

WHAT IT DOES

What sf_apex_test_run does on Salesforce CLI MCP Server

AI agents invoke sf_apex_test_run 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 sf_apex_test_run needs a policy

Running Apex tests triggers code execution in the Salesforce org. While typically read-only in intent, test execution can have side effects depending on test implementations (DML operations, callouts, etc.), making this an Execute-category action. Misuse could consume governor limits or trigger unintended org-side effects, warranting medium severity.

From the tool's definition 'Run Apex tests in a Salesforce org' — executes test code within a live Salesforce org environment

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

sf_apex_test_run Rate-limited

sf_apex_test_run 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": {
    "sf_apex_test_run": {
      "limits": [
        {
          "counter": "sf_apex_test_run_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 sf_apex_test_run

What does the sf_apex_test_run tool do? +

Run Apex tests in a Salesforce org. 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 sf_apex_test_run? +

Register the Salesforce CLI MCP Server MCP server in PolicyLayer and add a rule for sf_apex_test_run: 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 sf_apex_test_run? +

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

Can I rate-limit sf_apex_test_run? +

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

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

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