Run a read-only SQL query against the configured Aurora DSQL cluster. Aurora DSQL is distributed SQL database with Postgres compatibility. The following table summarizes `SELECT` functionality that is expected to work. Items not in this table may also be supported, as this is a point in time sna...
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 call readonly_query to retrieve information from AWS Labs Aurora DSQL MCP Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though readonly_query only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
readonly_query:
rules:
- action: allowSee the full AWS Labs Aurora DSQL MCP Server policy for all 7 tools.
Agents calling read-class tools like readonly_query have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Run a read-only SQL query against the configured Aurora DSQL cluster. Aurora DSQL is distributed SQL database with Postgres compatibility. The following table summarizes `SELECT` functionality that is expected to work. Items not in this table may also be supported, as this is a point in time snapshot. | Primary clause | Supported clauses | |---------------------------------|-----------------------| | FROM | | | GROUP BY | ALL, DISTINCT | | ORDER BY | ASC, DESC, NULLS | | LIMIT | | | DISTINCT | | | HAVING | | | USING | | | WITH (common table expressions) | | | INNER JOIN | ON | | OUTER JOIN | LEFT, RIGHT, FULL, ON | | CROSS JOIN | ON | | UNION | ALL | | INTERSECT | ALL | | EXCEPT | ALL | | OVER | RANK (), PARTITION BY | | FOR UPDATE | |. It is categorised as a Read tool in the AWS Labs Aurora DSQL MCP Server MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for readonly_query. 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.
readonly_query 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 readonly_query 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 readonly_query. 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.
readonly_query 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.