find_unused_log_groups
AI agents call find_unused_log_groups to retrieve information from AWS FinOps MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries AWS resources to identify unused log groups for cost optimization purposes—a read-only information retrieval operation with no capability to modify or delete resources. The 'find_*' verb pattern in AWS FinOps context consistently indicates discovery/analysis tools. While the empty description slightly lowers confidence, the context and sibling tools strongly suggest a read operation with low risk.
From the tool's definition Tool name 'find_unused_log_groups' indicates a search/discovery operation that retrieves information about AWS CloudWatch log groups based on usage patterns.
Attacks that exploit this kind of access
find_unused_log_groups. It is categorised as a Read tool in the AWS FinOps MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AWS FinOps MCP Server MCP server in PolicyLayer and add a rule for find_unused_log_groups: 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 FinOps MCP Server. Nothing to install.
find_unused_log_groups 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 find_unused_log_groups 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 find_unused_log_groups. 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.
find_unused_log_groups is provided by the AWS FinOps MCP Server MCP server (prashantgupta123/aws-pillar-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 →