scanner_run_dfa · Salesforce CLI MCP Server MCP

WHAT IT DOES

What scanner_run_dfa does on Salesforce CLI MCP Server

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

This tool executes the Salesforce Graph Engine (an external scanning/analysis tool) with arguments that can vary based on input parameters or files being analyzed. While its purpose is security analysis (benign intent), it triggers execution of external operations whose effects depend on the arguments provided (target files, scan configuration).

From the tool's definition Tool description states it "Run[s] Salesforce Graph Engine from a project to scan Apex code" and performs "path-based analysis to identify complex issues".

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

scanner_run_dfa Rate-limited

scanner_run_dfa 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": {
    "scanner_run_dfa": {
      "limits": [
        {
          "counter": "scanner_run_dfa_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 scanner_run_dfa

What does the scanner_run_dfa tool do? +

Run Salesforce Graph Engine from a project to scan Apex code for data flow analysis issues. This performs path-based analysis to identify complex issues like SQL injection, SOQL injection, and other security vulnerabilities. If any of the input parameters were not provided, then you choose them based on the target file or files. 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 scanner_run_dfa? +

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

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

Can I rate-limit scanner_run_dfa? +

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

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

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