run_secret_scan · Sentinel MCP Server MCP: Risk & Policy

WHAT IT DOES

What run_secret_scan does on Sentinel MCP Server

AI agents invoke run_secret_scan to trigger actions in Sentinel 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.

WHY IT NEEDS A POLICY

Why run_secret_scan needs a policy

This tool executes Gitleaks, a third-party secret detection utility, to scan for exposed credentials, API keys, and sensitive data in repositories. While not destructive itself, it triggers code execution of an external security scanner whose effects depend on the scan scope and target arguments provided.

From the tool's definition Tool name 'run_secret_scan' combined with description 'Run Secret scan using Gitleaks' indicates execution of an external scanning tool (Gitleaks) via Docker.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_secret_scan Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_secret_scan": {
      "limits": [
        {
          "counter": "run_secret_scan_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 Sentinel MCP Server, so you can run agents against it safely.

FAQ

Questions about run_secret_scan

What does the run_secret_scan tool do? +

Run Secret scan using Gitleaks. It is categorised as a Execute tool in the Sentinel 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_secret_scan? +

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

What risk level is run_secret_scan? +

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

Can I rate-limit run_secret_scan? +

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

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

run_secret_scan is provided by the Sentinel MCP Server MCP server (pranjal-lnct/scurity-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.