get_scan_findings

A read tool on the AWS MCP server.

SERVERAWS SOURCE@awslabs/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/aws/get-scan-findings.md

WHAT IT DOES

What get_scan_findings does on AWS

AI agents call get_scan_findings 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.

RISK

Why get_scan_findings is rated Low

The tool name contains 'get_', a standard pattern for read-only data retrieval. In the context of an AWS security/audit server, 'scan_findings' likely refers to security scan results (e.g., from AWS Inspector, Config, or similar services). Retrieval of security findings is a Read operation with no side effects.

From the tool's definition Tool name 'get_scan_findings' indicates retrieval of scan findings data with no mutation. Description is empty, limiting certainty.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_scan_findings 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_findings, this is the rule to start with:

get_scan_findings Allowed

get_scan_findings is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_scan_findings": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about get_scan_findings

What does the get_scan_findings tool do? +

get_scan_findings is a read tool on the AWS MCP server. It is categorised as a Read tool in the AWS MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_scan_findings? +

Register the AWS MCP server in PolicyLayer and add a rule for get_scan_findings: 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 get_scan_findings? +

get_scan_findings is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_scan_findings? +

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

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

get_scan_findings 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 →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →