security_scan · MCP Software Engineer MCP: Risk & Policy

WHAT IT DOES

What security_scan does on MCP Software Engineer

AI agents invoke security_scan to trigger actions in MCP Software Engineer. 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 security_scan needs a policy

Running a security scan actively executes scanning processes against codebases, dependencies, or infrastructure. This is an Execute-category action as it triggers external operations whose effects depend on arguments (what is being scanned).

From the tool's definition 'Run security vulnerability scan' - executes a scan operation against code or infrastructure

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

security_scan Rate-limited

security_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": {
    "security_scan": {
      "limits": [
        {
          "counter": "security_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 MCP Software Engineer, so you can run agents against it safely.

FAQ

Questions about security_scan

What does the security_scan tool do? +

Run security vulnerability scan. It is categorised as a Execute tool in the MCP Software Engineer MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on security_scan? +

Register the MCP Software Engineer MCP server in PolicyLayer and add a rule for security_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 MCP Software Engineer. Nothing to install.

What risk level is security_scan? +

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

Can I rate-limit security_scan? +

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

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

security_scan is provided by the MCP Software Engineer MCP server (rajawatrajat/mcp-software-engineer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.