AWS health check: 100-point scoring across EC2, S3, IAM MFA, and cost trends.
AI agents call aws_health_check to retrieve information from RedisNexus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and analyzes the health status and metrics of AWS services. It retrieves information about EC2 instances, S3 buckets, IAM MFA configuration, and cost data to generate a scoring report. No modifications, deletions, or resource provisioning are performed. The blast radius of misuse is low as it only exposes read access to monitoring data without operational side effects.
From the tool's definition Tool description explicitly states it performs 'health check' and '100-point scoring across EC2, S3, IAM MFA, and cost trends' - all read-only monitoring and assessment operations that retrieve status information without modifying infrastructure.
Attacks that exploit this kind of access
AWS health check: 100-point scoring across EC2, S3, IAM MFA, and cost trends. It is categorised as a Read tool in the RedisNexus MCP Server, which means it retrieves data without modifying state.
Register the RedisNexus MCP server in PolicyLayer and add a rule for aws_health_check: 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 RedisNexus. Nothing to install.
aws_health_check 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 aws_health_check 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 aws_health_check. 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.
aws_health_check is provided by the RedisNexus MCP server (rajkumar-madhu/mcp). 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 →