run_code_analyzer · Salesforce CLI MCP Server MCP

WHAT IT DOES

What run_code_analyzer does on Salesforce CLI MCP Server

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

This tool runs a code analysis engine against a codebase with configurable rules and filters. While primarily informational (Read-like in that it reports findings), the execution of static analysis rules, particularly with filtering flags for engines, constitutes triggering an external operation whose behavior depends on arguments. This crosses into Execute category.

From the tool's definition Tool description states 'Analyze your code from a project' and 'scan your codebase with...rules' using flags and engines.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_code_analyzer Rate-limited

run_code_analyzer 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_code_analyzer": {
      "limits": [
        {
          "counter": "run_code_analyzer_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_code_analyzer

What does the run_code_analyzer tool do? +

Analyze your code from a project with a selection of rules to ensure good coding practices. You can scan your codebase with the recommended rules. Or use flags to filter the rules based on engines (such as. 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_code_analyzer? +

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

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

Can I rate-limit run_code_analyzer? +

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

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

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