esm_msk_security_group
AI agents call esm_msk_security_group to retrieve information from Awslabs Valkey without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Without a description, classification is uncertain. The name pattern suggests a retrieval operation (querying security group settings) rather than modification or deletion. However, confidence is lowered due to lack of descriptive detail. Severity is low because security group reads typically have no side effects.
From the tool's definition Tool name 'esm_msk_security_group' suggests querying or retrieving security group configuration for MSK (Managed Streaming for Kafka), but description is empty.
Attacks that exploit this kind of access
esm_msk_security_group. It is categorised as a Read tool in the Awslabs Valkey MCP Server, which means it retrieves data without modifying state.
Register the Awslabs Valkey MCP server in PolicyLayer and add a rule for esm_msk_security_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 Awslabs Valkey. Nothing to install.
esm_msk_security_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 esm_msk_security_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 esm_msk_security_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.
esm_msk_security_group is provided by the Awslabs Valkey MCP server (awslabs.valkey-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.