get_group
AI agents call get_group 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.
Without a description, confidence is moderate. However, 'get_group' follows standard naming patterns for read operations (get, retrieve, fetch). The tool appears to query group information from ElastiCache Memcached or related AWS services, which would have no side effects. If it were destructive, executable, or modifying, the name would more likely reflect that intent.
From the tool's definition Tool name 'get_group' suggests retrieval of group data. Description is empty, limiting certainty, but the naming convention and context within an AWS management server indicates a query/fetch operation rather than modification or execution.
Attacks that exploit this kind of access
get_group. 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_group: 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_group 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_group 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_group. 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_group 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.