run_dast_scan · DevSecOps MCP Server MCP: Risk & Policy

WHAT IT DOES

What run_dast_scan does on DevSecOps MCP Server

AI agents invoke run_dast_scan to trigger actions in DevSecOps 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_dast_scan needs a policy

DAST tools perform dynamic testing by sending requests to running applications to identify vulnerabilities. This is an Execute operation because it triggers external testing operations whose side effects (network traffic, application state inspection, potential application behavior changes) depend on the scan arguments and target.

From the tool's definition Tool description states 'Execute DAST (Dynamic Application Security Testing) scan'. The verb 'Execute' combined with DAST scanning indicates the tool runs external security testing operations against applications whose effects depend on scan configuration and…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_dast_scan Rate-limited

run_dast_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_dast_scan": {
      "limits": [
        {
          "counter": "run_dast_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 DevSecOps MCP Server, so you can run agents against it safely.

FAQ

Questions about run_dast_scan

What does the run_dast_scan tool do? +

Execute DAST (Dynamic Application Security Testing) 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_dast_scan? +

Register the DevSecOps MCP Server MCP server in PolicyLayer and add a rule for run_dast_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_dast_scan? +

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

Can I rate-limit run_dast_scan? +

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

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

run_dast_scan is provided by the DevSecOps MCP Server MCP server (jesusdavidquarksoft/mcp_security). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.