Get query execution plan
AI agents call sqlserver_explain_query to retrieve information from Multi-Database MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The EXPLAIN/query plan feature retrieves structural and performance information about how a database would execute a query, but does not execute the query, modify data, delete records, or trigger external operations. This is a read-only diagnostic tool with minimal blast radius if misused—at worst it reveals query performance characteristics or schema information. Classification as Read is appropriate.
From the tool's definition Tool name 'explain_query' and description 'Get query execution plan' indicates retrieval of query metadata/analysis without data modification or execution of the query itself.
Attacks that exploit this kind of access
Get query execution plan. It is categorised as a Read tool in the Multi-Database MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Multi-Database MCP Server MCP server in PolicyLayer and add a rule for sqlserver_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 Multi-Database MCP Server. Nothing to install.
sqlserver_explain_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 sqlserver_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 sqlserver_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.
sqlserver_explain_query is provided by the Multi-Database MCP Server MCP server (nam088/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →