get_active_alarms
AI agents call get_active_alarms to retrieve information from Amazon ElastiCache Memcached MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves current alarm status from ElastiCache/AWS monitoring systems without creating, modifying, deleting, or executing any changes. This is consistent with Read category operations. Severity is low because viewing alarm status poses minimal risk—it provides operational visibility but not access to sensitive data or ability to alter resources.
From the tool's definition Tool name 'get_active_alarms' indicates retrieval of alarm state information with no modification capability. The naming pattern and sibling context (AWS monitoring/management tools) suggest query-only functionality.
Attacks that exploit this kind of access
get_active_alarms. It is categorised as a Read tool in the Amazon ElastiCache Memcached MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Amazon ElastiCache Memcached MCP Server MCP server in PolicyLayer and add a rule for get_active_alarms: 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 Amazon ElastiCache Memcached MCP Server. Nothing to install.
get_active_alarms 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 get_active_alarms 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 get_active_alarms. 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.
get_active_alarms is provided by the Amazon ElastiCache Memcached MCP Server MCP server (awslabs.memcached-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.