AI agents call dsql_lint as a supporting operation in Awslabs Valkey workflows.
The name 'dsql_lint' suggests static analysis or linting of DSQL (Distributed SQL) code, which would be a read-only operation with no side effects. However, the empty description provides no confirmation. Linting tools typically only analyze code without modifying data, placing this in the Read category at most, but given the extreme uncertainty from the empty description, 'Other' is assigned with low confidence.
From the tool's definition Tool description is empty and uninformative; the name 'dsql_lint' suggests a linting/analysis operation but cannot be confirmed.
Documented attack patterns abuse exactly the kind of access dsql_lint gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Awslabs Valkey, and nothing reaches the server without passing your rules. This is the rule we recommend for dsql_lint:
{
"version": "1",
"default": "deny",
"tools": {
"dsql_lint": {
"limits": [
{
"counter": "dsql_lint_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
}dsql_lint gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
dsql_lint. It is categorised as a Other tool in the Awslabs Valkey MCP Server, which means it performs auxiliary operations.
Register the Awslabs Valkey MCP server in PolicyLayer and add a rule for dsql_lint: 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_lint is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the dsql_lint 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_lint. 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_lint 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.
Start from Awslabs Valkey, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
805 Awslabs Valkey tools catalogued and risk-classified — across an index of 43,000+ MCP servers.