start_security_scan

A execute tool on the AWS MCP server.

SERVERAWS SOURCE@awslabs/mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/aws/start-security-scan.md

WHAT IT DOES

What start_security_scan does on AWS

AI agents invoke start_security_scan to trigger actions in AWS. 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.

RISK

Why start_security_scan is rated High

Security scanning is an external operation that triggers infrastructure scanning with effects dependent on configuration and scope. On AWS, security scans can examine resources, trigger API calls, and generate findings. This constitutes execution of a defined process rather than simple data retrieval. The high severity reflects that misconfigured scans could be noisy, resource-intensive, or expose sensitive findings.

From the tool's definition Tool name 'start_security_scan' indicates execution of a security scanning operation. The description is empty, limiting direct evidence.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs start_security_scan safely

PolicyLayer is an MCP gateway: it sits between your AI agents and AWS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For start_security_scan, this is the rule to start with:

start_security_scan Rate-limited

start_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": {
    "start_security_scan": {
      "limits": [
        {
          "counter": "start_security_scan_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect AWS, apply this rule, and every start_security_scan call is checked against it from then on.

FAQ

Questions about start_security_scan

What does the start_security_scan tool do? +

start_security_scan is a execute tool on the AWS MCP server. It is categorised as a Execute tool in the AWS MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on start_security_scan? +

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

What risk level is start_security_scan? +

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

Can I rate-limit start_security_scan? +

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

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

start_security_scan is provided by the AWS MCP server (@awslabs/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on AWS, and thousands of servers like it.

This server

All 300 AWS tools → High-risk tools on this server →

Across the catalogue

start_devtools_monitoring on Percepta MCP Server →team_manager_start_room on Team Manager MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →