Run Graph Engine for Apex data flow analysis. Detects complex security issues like SOQL/SQL injection.
AI agents invoke scanner_run_dfa 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.
This tool triggers execution of a static analysis engine (Graph Engine/DFA scanner) against Apex code. While the analysis itself is read-only in intent, the tool invokes an external analytical process whose execution and scope depend on provided arguments (which code to analyze, configuration parameters).
From the tool's definition The tool executes 'Graph Engine for Apex data flow analysis' which is a static analysis operation that runs code analysis tools on Apex code. The description states it 'detects complex security issues' indicating it performs complex computational analysis.
Documented attack patterns abuse exactly the kind of access scanner_run_dfa 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 scanner_run_dfa:
{
"version": "1",
"default": "deny",
"tools": {
"scanner_run_dfa": {
"limits": [
{
"counter": "scanner_run_dfa_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} 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.
Free to start. No card required.
Run Graph Engine for Apex data flow analysis. Detects complex security issues like SOQL/SQL injection. 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 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 MCP Server. Nothing to install.
scanner_run_dfa 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 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.
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.
scanner_run_dfa 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.