Find Route53 hosted zones with no query activity.
AI agents call find_unused_route53_hosted_zones 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 retrieves and analyzes data about Route53 hosted zones to identify those with no recent query activity. It performs a read-only assessment for cost optimization purposes (consistent with the FinOps focus), similar to sibling tools like 'analyze_rds_performance_insights' and 'analyze_api_gateway_performance' which are clearly informational queries.
From the tool's definition Tool name and description indicate it 'finds' or identifies Route53 hosted zones based on query activity status.
Attacks that exploit this kind of access
Find Route53 hosted zones with no query activity. 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_route53_hosted_zones: 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_route53_hosted_zones 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_route53_hosted_zones 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_route53_hosted_zones. 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_route53_hosted_zones 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 →