sf_scan_apex_antipatterns
Scans Apex classes in the org for common anti-patterns using the Tooling API. Detects SOQL/DML in loops, hardcoded Salesforce IDs, and debug statements left in production code. Use before deploying to catch performance and quality issues early. classNames: optional list of class names to scan (om...
This record as markdown: /tools/io-github-semwalajay83-sem-salesforce-metadata-mcp/sf-scan-apex-antipatterns.md
What sf_scan_apex_antipatterns does on Salesforce Metadata Mcp
AI agents call sf_scan_apex_antipatterns to retrieve information from Salesforce Metadata Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why sf_scan_apex_antipatterns is rated Low
This tool retrieves and analyzes metadata (Apex class definitions) to identify code quality issues. It has optional filtering parameters (classNames, maxClasses) but performs only read-only inspection via the Tooling API. No modifications are made to the scanned classes, no code is executed, and the output is informational. This is a static analysis/audit tool with negligible blast radius if misused.
From the tool's definition Scans Apex classes for anti-patterns using the Tooling API. The tool "Detects SOQL/DML in loops, hardcoded Salesforce IDs, and debug statements" - it performs analysis and reporting only, with no parameters that modify, execute, or delete code.
Attacks that exploit this kind of access
The rule that runs sf_scan_apex_antipatterns safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Salesforce Metadata Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sf_scan_apex_antipatterns, this is the rule to start with:
sf_scan_apex_antipatterns is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Salesforce Metadata Mcp, apply this rule, and every sf_scan_apex_antipatterns call is checked against it from then on.
Questions about sf_scan_apex_antipatterns
Scans Apex classes in the org for common anti-patterns using the Tooling API. Detects SOQL/DML in loops, hardcoded Salesforce IDs, and debug statements left in production code. Use before deploying to catch performance and quality issues early. classNames: optional list of class names to scan (omits test classes with __Test suffix) maxClasses: maximum classes to scan (default 20, max 200). It is categorised as a Read tool in the Salesforce Metadata Mcp MCP Server, which means it retrieves data without modifying state.
Register the Salesforce Metadata MCP server in PolicyLayer and add a rule for sf_scan_apex_antipatterns: 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 Metadata Mcp. Nothing to install.
sf_scan_apex_antipatterns is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the sf_scan_apex_antipatterns 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 sf_scan_apex_antipatterns. 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.
sf_scan_apex_antipatterns is provided by the Salesforce Metadata MCP server (salesforce-metadata-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Salesforce Metadata, and thousands of servers like it.
This server
Across the catalogue