find_unused_load_balancers
AI agents call find_unused_load_balancers 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 discovers unused load balancers by querying AWS infrastructure metadata—a read-only operation with no side effects. While the description is uninformative, the sibling tools and server purpose (cost optimization and monitoring) confirm this is a data retrieval function. No modification, deletion, execution, or financial impact occurs.
From the tool's definition Tool name 'find_unused_load_balancers' indicates a search/discovery operation. Sibling tools on the server (analyze_*, find_*) are all read-only queries that identify and analyze AWS resources without modifying them.
Attacks that exploit this kind of access
find_unused_load_balancers. 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_load_balancers: 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_load_balancers 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_load_balancers 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_load_balancers. 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_load_balancers 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 →