Validate SQL for Aurora DSQL compatibility and optionally auto-fix issues. Parses SQL and reports compatibility errors (unsupported syntax) with suggested fixes. Use fix=True to generate DSQL-compatible SQL automatically. ## When to Use - Before executing any externally-sourced SQL (ORM migrati...
Accepts freeform code/query input (sql)
Part of the AWS Labs Aurora DSQL MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use dsql_lint to create or modify resources in AWS Labs Aurora DSQL MCP Server. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call dsql_lint repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach AWS Labs Aurora DSQL MCP Server.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
dsql_lint:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full AWS Labs Aurora DSQL MCP Server policy for all 7 tools.
Agents calling write-class tools like dsql_lint have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Validate SQL for Aurora DSQL compatibility and optionally auto-fix issues. Parses SQL and reports compatibility errors (unsupported syntax) with suggested fixes. Use fix=True to generate DSQL-compatible SQL automatically. ## When to Use - Before executing any externally-sourced SQL (ORM migrations, pg_dump, hand-written DDL) - When migrating schemas from PostgreSQL, MySQL, or other databases to DSQL - To validate CREATE TABLE, ALTER TABLE, CREATE INDEX, and other DDL statements - To check transaction structure (DSQL requires one DDL per transaction) ## Fix Behavior When fix=True, each diagnostic carries a `fix_result.status`: - `fixed`: safe mechanical transformation applied - `fixed_with_warning`: fix applied but may require application code changes - unfixable diagnostics have no `fix_result` and require manual intervention. It is categorised as a Write tool in the AWS Labs Aurora DSQL MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for dsql_lint. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the AWS Labs Aurora DSQL MCP Server MCP server.
dsql_lint is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the dsql_lint rule in your Intercept 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 Intercept 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 AWS Labs Aurora DSQL MCP Server MCP server (awslabs.aurora-dsql-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.