Get recommendations for DSQL best practices
AI agents call dsql_recommend 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 retrieves advisory information (recommendations) without side effects. It does not create, modify, execute commands, delete data, or involve financial operations. The action is purely informational and read-based.
From the tool's definition Tool name 'dsql_recommend' and description 'Get recommendations for DSQL best practices' indicate a read-only operation that retrieves or queries best practice recommendations without modifying, executing, or deleting any data.
Attacks that exploit this kind of access
Get recommendations for DSQL 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 dsql_recommend: 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.
dsql_recommend 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 dsql_recommend 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 dsql_recommend. 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.
dsql_recommend 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.