Run Apex tests in a Salesforce Org. 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.
AI agents invoke run_apex_tests to trigger actions in Salesforce 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.
The tool executes arbitrary test code within a Salesforce organization. While tests are intended to be non-destructive, they execute code that can have side effects depending on test implementation (database modifications, API calls, etc.). This is Execute rather than Write because it runs code whose behavior is determined by arguments and existing code, not merely creating/modifying data directly.
From the tool's definition Tool runs Apex tests via 'execute unit tests' with options for 'test level, specific classes, suites' and 'code coverage collection.' Apex test execution is a form of code execution that triggers external operations within the Salesforce org whose effects…
Documented attack patterns abuse exactly the kind of access run_apex_tests gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Salesforce MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for run_apex_tests:
{
"version": "1",
"default": "deny",
"tools": {
"run_apex_tests": {
"limits": [
{
"counter": "run_apex_tests_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Run Apex tests in a Salesforce Org. 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 MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Salesforce 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 MCP Server. Nothing to install.
run_apex_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 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.
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.
run_apex_tests is provided by the Salesforce MCP Server MCP server (advancedcommunities/salesforce-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Salesforce MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
41 Salesforce MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.