scan_repo_and_wait · Trust Security MCP: Risk & Policy

WHAT IT DOES

What scan_repo_and_wait does on Trust Security

AI agents invoke scan_repo_and_wait to trigger actions in Trust Security. 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_repo_and_wait needs a policy

The tool name strongly implies it triggers an automated security scan of a repository and waits for results, similar to sibling tools 'scan_repo' and 'scan_and_wait'. This constitutes executing an external operation (SAST scan) against a target repository. The description is empty, which lowers confidence, but the naming pattern and server context make this classification highly likely.

From the tool's definition Tool name 'scan_repo_and_wait' and sibling tools context ('scan_repo', 'scan_and_wait', SAST scanning of GitHub repositories)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

scan_repo_and_wait Rate-limited

scan_repo_and_wait 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_repo_and_wait": {
      "limits": [
        {
          "counter": "scan_repo_and_wait_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 Trust Security, so you can run agents against it safely.

FAQ

Questions about scan_repo_and_wait

What does the scan_repo_and_wait tool do? +

scan_repo_and_wait. It is categorised as a Execute tool in the Trust Security 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_repo_and_wait? +

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

What risk level is scan_repo_and_wait? +

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

Can I rate-limit scan_repo_and_wait? +

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

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

scan_repo_and_wait is provided by the Trust Security MCP server (jaden-jjh/trust-security-scanner). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.