AI agents invoke explain_query to trigger actions in Redshift MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
On Redshift, EXPLAIN runs a query through the planner and returns the execution plan without executing DML — however, the tool could accept arbitrary SQL and pass it to EXPLAIN, which still involves sending SQL to the database engine. Given the empty description and sibling tool 'run_query', this tool likely executes EXPLAIN <sql> statements.
From the tool's definition Tool name 'explain_query' and server context 'execution plan analysis' suggest it runs EXPLAIN against SQL queries in Redshift. Description is empty, lowering confidence.
Documented attack patterns abuse exactly the kind of access explain_query gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Redshift MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for explain_query:
{
"version": "1",
"default": "deny",
"tools": {
"explain_query": {
"limits": [
{
"counter": "explain_query_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}explain_query stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
explain_query. It is categorised as a Execute tool in the Redshift MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Redshift MCP Server MCP server in PolicyLayer and add a rule for explain_query: 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 Redshift MCP Server. Nothing to install.
explain_query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the explain_query 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 explain_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.
explain_query is provided by the Redshift MCP Server MCP server (tuanknguyen/redshift-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Redshift MCP Server, 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.
5 Redshift MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.