GetCodeConnection
AI agents call GetCodeConnection 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, confidence is reduced from typical levels. The 'Get' prefix strongly suggests this is a retrieval operation (Read category). Given it appears to be querying AWS infrastructure configuration rather than executing commands or making modifications, Read is the most probable classification.
From the tool's definition Tool name 'GetCodeConnection' with no description provided suggests retrieval of connection configuration or metadata. The 'Get' prefix indicates a read operation rather than modification or execution.
Attacks that exploit this kind of access
GetCodeConnection. 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 GetCodeConnection: 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.
GetCodeConnection 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 GetCodeConnection 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 GetCodeConnection. 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.
GetCodeConnection 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.