run_iast_scan · DevSecOps MCP Server MCP: Risk & Policy

WHAT IT DOES

What run_iast_scan does on DevSecOps MCP Server

AI agents invoke run_iast_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_iast_scan needs a policy

This tool executes an IAST scanner, which performs runtime analysis by instrumenting code and inspecting application behavior during execution. While it's a security tool (non-malicious intent), execution of external programs with configurable parameters falls under the Execute category.

From the tool's definition Tool name contains 'run_' verb and description states 'Execute IAST (Runtime Configuration & Header Analysis) scan' — explicitly indicates execution of an external security scanning tool with runtime effects.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_iast_scan Rate-limited

run_iast_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_iast_scan": {
      "limits": [
        {
          "counter": "run_iast_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_iast_scan

What does the run_iast_scan tool do? +

Execute IAST (Runtime Configuration & Header Analysis) 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_iast_scan? +

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

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

Can I rate-limit run_iast_scan? +

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

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

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