Analyze CloudFront cache hit ratios.
AI agents call analyze_cloudfront_cache_hit_ratio 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 existing CloudFront performance metrics (cache hit ratios). It does not create, modify, delete, or execute any operations—it simply queries and presents CloudFront performance data. This is a classic Read operation used for observability and optimization insights.
From the tool's definition Tool name 'analyze_cloudfront_cache_hit_ratio' and description 'Analyze CloudFront cache hit ratios' indicate data retrieval and analysis only.
Attacks that exploit this kind of access
Analyze CloudFront cache hit ratios. 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 analyze_cloudfront_cache_hit_ratio: 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.
analyze_cloudfront_cache_hit_ratio 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 analyze_cloudfront_cache_hit_ratio 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 analyze_cloudfront_cache_hit_ratio. 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.
analyze_cloudfront_cache_hit_ratio 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 →