run_sca_scan

THE RISK

High Risk

Why run_sca_scan needs a policy

This tool executes an external operation (SCA scan) that analyzes software dependencies and generates security findings. While the scan itself is non-destructive and read-focused in intent, the tool *runs* a scanning operation on an AI agent's behalf.

From the tool's definition Tool name states 'run_sca_scan' with description 'Execute SCA (Software Composition Analysis) scan'. The verb 'Execute' combined with 'run' indicates the tool triggers an external security scanning operation whose effects (scan results, dependency analysis,…

Documented attack patterns abuse exactly the kind of access run_sca_scan gives an agent:

POLICY

How to control run_sca_scan

PolicyLayer is an MCP gateway — it sits between your AI agents and DevSecOps MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for run_sca_scan:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_sca_scan": {
      "limits": [
        {
          "counter": "run_sca_scan_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

Create a free account and register DevSecOps MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More DevSecOps MCP Server tools

Execute run_dast_scan Execute DAST (Dynamic Application Security Testing) scan Execute run_iast_scan Execute IAST (Interactive Application Security Testing) scan Execute run_sast_scan Execute SAST (Static Application Security Testing) scan Read validate_security_policy Validate security policy compliance Read generate_security_report Generate comprehensive security report from all scans

All 6 DevSecOps MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in DevSecOps MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about run_sca_scan

What does the run_sca_scan tool do? +

Execute SCA (Software Composition Analysis) scan. It is categorised as a Execute tool in the DevSecOps 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_sca_scan? +

Register the DevSecOps MCP Server MCP server in PolicyLayer and add a rule for run_sca_scan: 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 DevSecOps MCP Server. Nothing to install.

What risk level is run_sca_scan? +

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

Can I rate-limit run_sca_scan? +

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

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

run_sca_scan is provided by the DevSecOps MCP Server MCP server (jmstar85/devsecops-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every DevSecOps MCP Server tool call.

Start from DevSecOps MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →