cdk_best_practices
AI agents call cdk_best_practices 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.
The name implies a tool that retrieves or analyzes best practices guidance for AWS CDK projects. Without a description, confidence is reduced, but the naming convention and sibling tool patterns (heavy on 'analyze' operations) indicate this is likely a read-only analytical tool that queries or retrieves information rather than modifying state or executing code.
From the tool's definition Tool name 'cdk_best_practices' suggests analysis or retrieval of best practice information. No description provided to confirm function.
Attacks that exploit this kind of access
cdk_best_practices. 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 cdk_best_practices: 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.
cdk_best_practices 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 cdk_best_practices 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 cdk_best_practices. 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.
cdk_best_practices 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.