Execute SAST (Static Application Security Testing) scan
AI agents invoke run_sast_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.
This tool triggers execution of static application security testing against code. While SAST scans are non-destructive and read-focused in intent, the 'Execute' verb combined with 'scan' indicates the tool runs an external security analysis process whose resource consumption and side effects (logs, reports, temporary artifacts) depend on the codebase being scanned.
From the tool's definition Tool name 'run_sast_scan' with description 'Execute SAST (Static Application Security Testing) scan' indicates execution of a security scanning operation.
Documented attack patterns abuse exactly the kind of access run_sast_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_sast_scan:
{
"version": "1",
"default": "deny",
"tools": {
"run_sast_scan": {
"limits": [
{
"counter": "run_sast_scan_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}run_sast_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 SAST (Static 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_sast_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_sast_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_sast_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_sast_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_sast_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.