get-ssh-tunnel-command-replication-group
AI agents call get-ssh-tunnel-command-replication-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.
This tool appears to retrieve or generate SSH tunnel commands for accessing an ElastiCache/MemoryDB replication group. This is a Read operation—it queries or retrieves configuration/connection information without modifying state. The tool does not execute the tunnel (which would be Execute), nor does it modify or delete data.
From the tool's definition Tool name 'get-ssh-tunnel-command-replication-group' contains 'get' which is a retrieval operation. The name suggests it retrieves or generates SSH tunnel connection information for a replication group.
Attacks that exploit this kind of access
get-ssh-tunnel-command-replication-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 get-ssh-tunnel-command-replication-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.
get-ssh-tunnel-command-replication-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-ssh-tunnel-command-replication-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-ssh-tunnel-command-replication-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-ssh-tunnel-command-replication-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.