dsql_lint
AI agents call dsql_lint as a supporting operation in Amazon MQ MCP Server workflows.
The description is empty and uninformative. The name 'dsql_lint' suggests a linting or static analysis tool (possibly for DSQL/distributed SQL), which would be a Read/Execute category, but without confirmation I default to Other with low confidence. Lint tools generally only read and analyze code without side effects, so severity is low.
From the tool's definition Tool name 'dsql_lint' and empty description provide no clear indication of what the tool does. 'lint' typically implies static analysis/read-only checks, but this cannot be confirmed.
Attacks that exploit this kind of access
dsql_lint. It is categorised as a Other tool in the Amazon MQ MCP Server MCP Server, which means it performs auxiliary operations.
Register the Amazon MQ MCP Server 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 Amazon MQ MCP Server. 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 Amazon MQ MCP Server MCP server (awslabs.amazon-mq-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.