Lists recent high-severity GuardDuty findings.
AI agents call list_guardduty_findings to retrieve information from AWS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a data retrieval operation (list/query) on AWS GuardDuty findings. It has no side effects—it does not create, modify, delete, or execute any actions. The server is explicitly described as 'read-only,' and this tool's function aligns with that constraint.
From the tool's definition Tool name 'list_guardduty_findings' and description 'Lists recent high-severity GuardDuty findings' indicate a read-only operation that retrieves and queries security findings data with no modification or deletion capability.
Attacks that exploit this kind of access
Lists recent high-severity GuardDuty findings. It is categorised as a Read tool in the AWS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AWS MCP Server MCP server in PolicyLayer and add a rule for list_guardduty_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 MCP Server. Nothing to install.
list_guardduty_findings 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 list_guardduty_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.
Set action: deny in the PolicyLayer policy for list_guardduty_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.
list_guardduty_findings is provided by the AWS MCP Server MCP server (sergiosediq/aws-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →