scan_all · Secscan MCP: Risk & Policy

WHAT IT DOES

What scan_all does on Secscan

AI agents invoke scan_all to trigger actions in Secscan. 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 scan_all needs a policy

This tool executes multiple scanning operations (secrets detection, SAST analysis, dependency scanning, IaC misconfiguration checks) against a codebase. It runs external tools and processes code, making it an Execute-category tool.

From the tool's definition "Run every installed scanner (secrets, SAST, dependencies, IaC)" — triggers execution of multiple scanning tools across the codebase

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

scan_all Rate-limited

scan_all 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": {
    "scan_all": {
      "limits": [
        {
          "counter": "scan_all_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 Secscan, so you can run agents against it safely.

FAQ

Questions about scan_all

What does the scan_all tool do? +

Run every installed scanner (secrets, SAST, dependencies, IaC) and return. It is categorised as a Execute tool in the Secscan MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on scan_all? +

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

What risk level is scan_all? +

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

Can I rate-limit scan_all? +

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

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

scan_all is provided by the Secscan MCP server (openjkai/secscan_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.