get_scan_status
Check the status of a security scan. Useful for checking a previous scan from an earlier session, or verifying a scan completed after session recovery.
This record as markdown: /tools/aws/get-scan-status.md
What get_scan_status does on AWS
AI agents call get_scan_status to retrieve information from AWS without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_scan_status is rated Low
This tool retrieves the state of an existing security scan. It has no side effects, does not trigger new actions, and does not modify data. It is a simple read operation typical of status-checking utilities. The low severity reflects minimal risk even if misused by an agent—querying scan status cannot cause harm.
From the tool's definition Tool name 'get_scan_status' and description 'Check the status of a security scan' indicate a query operation that retrieves status information without modifying or executing any operations.
Attacks that exploit this kind of access
The rule that runs get_scan_status 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 get_scan_status, this is the rule to start with:
get_scan_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect AWS, apply this rule, and every get_scan_status call is checked against it from then on.
Questions about get_scan_status
Check the status of a security scan. Useful for checking a previous scan from an earlier session, or verifying a scan completed after session recovery. It is categorised as a Read tool in the AWS MCP Server, which means it retrieves data without modifying state.
Register the AWS MCP server in PolicyLayer and add a rule for get_scan_status: 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.
get_scan_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_scan_status 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 get_scan_status. 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.
get_scan_status 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.
More on AWS, and thousands of servers like it.
This server
Across the catalogue