Skip to main content
Glama
@squirex.dev/mcp-server

@squirex.dev/mcp-server

Official
by SquireX-dev

@squirex.dev/mcp-server

SquireX MCP Server — Agentforce Capability Scanner for AI Coding Agents

npm version License

Model Context Protocol server exposing the SquireX Agentforce Capability Scanner to AI-powered developer tools. Works with Claude Code, Gemini, GitHub Copilot, and any MCP-compatible IDE.


Why SquireX?

Salesforce Agentforce agents use LLMs to autonomously execute Apex, Flows, and external services. Without guardrails, this creates OWASP LLM Top 10 vulnerabilities:

  • šŸ”“ Excessive Agency — Agents that modify data without user confirmation

  • šŸ”“ Prompt Injection — User input that hijacks agent instructions

  • šŸ”“ Privilege Escalation — Actions running in system context without sharing

  • 🟠 Supply Chain — Stale API versions that silently skip metadata types

SquireX scans your Agentforce metadata with 61+ SAST rules across 27 categories and integrates directly into your AI coding workflow.


Related MCP server: frogeye-mcp

Quick Start

Add to your AI IDE configuration (Claude Code, Gemini, VS Code, JetBrains):

{
  "mcpServers": {
    "squirex": {
      "command": "npx",
      "args": ["-y", "@squirex.dev/mcp-server"],
      "env": {
        "SQUIREX_PROJECT_DIR": "/path/to/your/salesforce/project"
      }
    }
  }
}

That's it. Your AI agent now has access to the Agentforce Capability Scanner.


MCP Surface

Tools (16)

Core Scanning (Primary Value)

Tool

Description

scan_agentforce

Run all 61+ SAST rules against the project. Returns SARIF.

scan_agentforce_file

Scan a single metadata file (.genAiFunction-meta.xml, .agent, etc.)

scan_agentforce_rule

Run a specific rule (e.g., AGENTFORCE-1.1)

Rule Intelligence

Tool

Description

list_scan_rules

List all 61+ rules with ID, category, severity

get_rule_details

Deep dive: description + remediation guidance

explain_violation

Root-cause analysis for a specific violation

suggest_fix

Generate a code/metadata fix suggestion

Apex Testing & Schema

Tool

Description

run_tests

Execute Apex tests locally using the Go interpreter

get_coverage

Extract line-level code coverage data

analyze_schema

Aggregate inferred SObject schema from the codebase

predict_conflicts

Predict merge conflicts between branches

generate_sarif_report

Generate SARIF for CI/CD pipeline integration

Testing Center Bridge

Tool

Description

generate_dx_tests

Convert scan violations → Agentforce DX test YAML for Testing Center

validate_dx_tests

Validate DX test spec syntax and schema

push_to_testing_center

Push test spec to Salesforce via sf agent test run

get_testing_center_results

Get status/results of a Testing Center test run

Resources (6)

URI

Description

squirex://scan/rules

Complete 51+ rule catalog

squirex://scan/rules/{id}

Rule detail with remediation

squirex://scan/results/latest

Latest scan results (SARIF)

squirex://schema/objects

Inferred SObject schema

squirex://test-results/latest

Latest Apex test results

squirex://coverage/latest

Latest code coverage

Prompts (4)

Prompt

What It Does

review-agentforce-security

Full 51+ rule scan → prioritized remediation plan

fix-agentforce-violation

Diagnose + fix a specific violation

harden-agent-metadata

Proactive defense-in-depth review

generate-test-evaluation

Generate Agentforce DX test YAML specs for Testing Center


Agentforce Capability Scanner — 61+ Rules

#

Category

Rules

Severity

1

Action Configuration

Mandatory Confirmation, Schema Sync, Privilege Analysis

šŸ”“ Critical / 🟠 High

2

Agent Script Safety

Validation Guards, Transition Integrity, Prompt Injection Defense

šŸ”“ Critical / 🟠 High

3

Grounding Security

Hardcoded Secrets, FLS Masking Alignment

šŸ”“ Critical / 🟠 High

4

Structural Dependency

Planner Completeness, Deactivation Collision, Evaluation Governance

🟠 High / 🟔 Medium

5

Flow Security

Flow Context/Silent State/Injection, API Injection, PT Poisoning/Activation

šŸ”“ Critical / 🟠 High

6

Supply Chain Security

API Downgrade, Schema Desync, Managed Package Origin

🟠 High / 🟔 Medium

7

Agentic Architecture

Topic Bloat, Skill Semantics, Orphaned Bot Evaluation

🟠 High / 🟔 Medium

9

Instruction Integrity

Metadata Instruction Poisoning, Cross-Topic Boundary

šŸ”“ Critical / 🟠 High

10

Operational Reliability

Validation Conflict

🟔 Medium

11

Autonomous Scheduling

Unguarded Scheduled Action, Time-Window Privilege Drift

šŸ”“ Critical / 🟠 High

12

Copilot Studio Config

Memory Poisoning, API Version Drift

šŸ”“ Critical

13

Data Cloud Grounding

RAG Without Schema Classification

šŸ”“ Critical

14

Slack Integration

Slack Bot Without DLP Guard

🟠 High

15

External Service Security

Certificate Pinning, Dynamic Cloaking RAG

🟠 High

16

Custom Permission

Agent Action Without Permission Gate

🟠 High

17

Commerce

Idempotency Key, Amount Bounds Check

šŸ”“ Critical

18

Multi-Agent Orchestration

Compositional Fragment Trap, Sybil Identity

šŸ”“ Critical / 🟠 High

19

Platform Event / CDC

Sub-agent Spawning Loop, CDC Field Filter

šŸ”“ Critical / 🟠 High

20–24

OWASP LLM Top 10

Excessive Agency, Data Exfil, SSRF, DoS, MCP Auth

šŸ”“ Critical / 🟠 High

30–34

Enterprise Graph

PII Graph, Privilege Graph, Blast Radius, MCP Scope, XSS Graph

šŸ”“ Critical / 🟠 High


Supported Metadata Types

  • .genAiFunction-meta.xml

  • .genAiPlugin-meta.xml

  • .genAiPlannerBundle-meta.xml

  • .genAiPromptTemplate-meta.xml

  • .genAiPromptTemplateActv-meta.xml

  • .agent files

  • .cls (Apex classes)

  • .trigger (Apex triggers)

  • .namedCredential-meta.xml

  • .connectedApp-meta.xml

  • .field-meta.xml

  • .aiEvaluationDefinition-meta.xml

  • .flow-meta.xml

  • schema.json

  • sfdx-project.json

  • package.xml

  • LWC components (.js in lwc/ dirs)


How It Works

AI Coding Agent (Claude / Gemini / Copilot)
        │
        │ MCP Protocol (stdio)
        ā–¼
ā”Œā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”
│ @squirex.dev/mcp-server │ ← This package
│  16 tools, 6 resources  │
│  4 prompts              │
ā””ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”¬ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”˜
        │ spawn
        ā–¼
ā”Œā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”
│   squirex CLI            │
│   scan / generate-tests  │ ← Testing Center bridge
ā””ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”¬ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”˜
        │ JSON IPC
        ā–¼
ā”Œā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”      ā”Œā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”
│   squireinterp           │      │   sf agent test run  │
│   Go Execution Engine    │      │   (Salesforce CLI)   │
│   61+ SAST Rules         │      │   → Testing Center   │
ā””ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”˜      ā””ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”˜

The Testing Center bridge tools delegate to squirex generate-tests, which:

  1. Runs a capability scan (or reads existing SARIF)

  2. Converts violations to Agentforce DX test YAML (all 61+ rules, normalized AGENTFORCE-X.Y IDs)

  3. Optionally validates and pushes to the Salesforce Testing Center via sf agent test run


Requirements

  • Node.js ≄ 18

  • squirex CLI installed (or available via npx)

  • A Salesforce project with Agentforce metadata


GitHub App Integration

For automated PR scanning, install the SquireX GitHub App — one-click setup, 51+ rule scan on every pull request, SARIF in your Security tab.

Plan

Public Repos

Private Repos

Price

Free

Unlimited

—

$0

Pro

Unlimited

1

$49/repo/month

Enterprise

Unlimited

Unlimited

$299/org/month


License

Proprietary — See LICENSE.md

Copyright Ā© 2026 SquireX. All Rights Reserved.


⚔ Built by SquireX — Securing the AI Agent Pipeline

Available Tools

16 tools
analyze_schemaA

Aggregate and analyze the inferred schema from all Apex classes in the project. Returns SObject definitions, field usage heatmaps, and relationship graphs. Useful for understanding the data model without an org connection.

Inputs: directory, includeHeatmap.

explain_violationA

Given a SARIF violation from a scan, provide root-cause analysis and step-by-step remediation guidance. Pass the full violation object or just the ruleId and file path.

Inputs: ruleId (required), message, filePath, lineNumber.

generate_dx_testsA

Convert Agentforce scan violations into Agentforce DX test specifications (YAML format) compatible with sf agent test run and the Salesforce Testing Center. Delegates to the core SquireX CLI generate-tests command. If no SARIF file is provided, runs a fresh scan first.

Inputs: rules, sarifPath, suiteName, outputPath.

generate_sarif_reportA

Generate a SARIF (Static Analysis Results Interchange Format) report from the Agentforce Capability Scan. SARIF is the standard format for GitHub Security tab, Azure DevOps, and other CI/CD integrations.

Inputs: outputPath.

get_coverageA

Extract code coverage data from the most recent test run. Shows covered/uncovered lines per class.

Inputs: className.

get_rule_detailsA

Get detailed information about a specific Agentforce SAST rule including its description, severity, and remediation guidance.

Inputs: ruleId (required).

get_testing_center_resultsA

Get the status and results of a previously submitted Agentforce Test Run from the Testing Center. Requires an authenticated Salesforce org.

Inputs: targetOrg (required), testRunId (required).

list_scan_rulesA

List all 26 Agentforce Capability Scanner rules with their ID, name, category, severity, and description. Use this to understand the full scope of the security scan.

Inputs: category, severity.

predict_conflictsB

Predict merge conflicts between two branches by analyzing Apex class changes, DML patterns, and metadata dependencies. Helps prevent deployment failures.

Inputs: branches (required), simulate.

push_to_testing_centerA

Push an Agentforce DX test spec to the Salesforce Testing Center. Delegates to squirex generate-tests --push --target-org <org>. Requires an authenticated Salesforce org with sf org login and the Agentforce DX plugin.

Inputs: targetOrg (required), testFilePath (required).

run_testsA

Execute Apex tests locally using the high-fidelity Go interpreter. Returns structured test results with pass/fail status, assertion details, stack traces, and line-level code coverage.

Inputs: file, filter, failFast, parallel.

scan_agentforceA

Run the full Agentforce Capability Scan (26 SAST rules across 9 categories) against the current project. Returns SARIF-structured violations covering action configuration, agent script safety, grounding security, structural dependencies, flow/prompt template security, supply chain, agentic architecture, instruction integrity, and operational reliability.

Inputs: directory, baseBranch.

scan_agentforce_fileA

Scan a specific Agentforce metadata file for capability violations. Supports .genAiFunction-meta.xml, .genAiPlugin-meta.xml, .genAiPlannerBundle-meta.xml, .genAiPromptTemplate-meta.xml, .agent files, .cls (Apex), .trigger, and schema.json files.

Inputs: filePath (required).

scan_agentforce_ruleA

Run a single Agentforce SAST rule against the project. Useful for focused analysis. Rule IDs follow the pattern AGENTFORCE-X.Y (e.g., AGENTFORCE-1.1 for Mandatory User Confirmation).

Inputs: ruleId (required).

suggest_fixA

Given a specific Agentforce violation (rule ID + file), generate a suggested metadata or code fix. Returns a diff-style suggestion.

Inputs: ruleId (required), filePath (required), violationContext.

validate_dx_testsA

Validate a generated Agentforce DX test spec without executing it. Delegates to squirex generate-tests --validate. Requires Salesforce CLI with Agentforce DX support.

Inputs: testFilePath (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 16 tools

    Disambiguation4/5

    Most tools have clear, distinct scopes (scan whole project vs. specific file vs. specific rule; explain vs. suggest fix). The only minor overlap is between scan_agentforce and generate_sarif_report, both of which output SARIF, which could cause an agent to pick the wrong one when a report artifact is needed.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with lowercase and underscores (scan_agentforce, list_scan_rules, generate_sarif_report, push_to_testing_center). The verbs are predictable and clearly indicate the action, making the set easy to navigate.

    Tool Count4/5

    With 16 tools, the server is slightly over the typical 3-15 well-scoped range, but each tool serves a distinct purpose within the two main workflows (scanning and testing). The count feels justified and not bloated, so it earns a 4 rather than a 3.

    Completeness4/5

    The tool surface covers the full scanning lifecycle (run scans, list rules, get details, generate reports, explain and suggest fixes) and the testing workflow (run tests, get coverage, generate/validate/push test specs, retrieve results). Minor gaps include no direct way to apply suggested fixes or retrieve historical scan results, but these are workable.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      D
      maintenance
      An MCP server that integrates SAST, DAST, and SCA security tools to enable AI-driven vulnerability scanning and automated security reporting. It allows AI assistants to execute and analyze results from tools like Semgrep, OWASP ZAP, and Trivy within a DevSecOps workflow.
      6
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      AI-powered security vulnerability detection for MCP-compatible agents, offering real-time scanning of code against a knowledge graph of 24,000+ vulnerability patterns.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that securely reviews AI-generated code for vulnerabilities such as SQL injection, command injection, and hardcoded credentials.
      12
      Apache 2.0