Execute DAST (Dynamic Application Security Testing) scan
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.
DAST scans actively interact with running applications by sending requests and analyzing responses to identify vulnerabilities. This is an Execute category tool because it runs external security testing operations. Severity is high because misconfigured or malicious DAST scans could disrupt target systems, cause denial of service, or trigger unintended side effects on production applications.
From the tool's definition Tool name 'run_dast_scan' and description 'Execute DAST (Dynamic Application Security Testing) scan' indicate execution of external security testing operations against target applications.
Documented attack patterns abuse exactly the kind of access run_dast_scan gives an agent:
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_dast_scan:
{
"version": "1",
"default": "deny",
"tools": {
"run_dast_scan": {
"limits": [
{
"counter": "run_dast_scan_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
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.
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.
run_dast_scan is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
run_dast_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.
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.
Free to start. No card required.
6 DevSecOps MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.