Get the execution plan for a SQL query
AI agents call explain_query to retrieve information from SQL Server MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Execution plans are metadata/diagnostic information about how a database engine would or did execute a query. They do not retrieve user data, modify records, delete data, or trigger external operations. This is a pure read operation used for performance analysis and optimization. The tool has minimal blast radius if misused by an AI agent.
From the tool's definition Tool name is 'explain_query' and description states it 'Get the execution plan for a SQL query' — execution plans are read-only analysis outputs that examine query structure without executing the query against live data or modifying any state.
Attacks that exploit this kind of access
Get the execution plan for a SQL query. It is categorised as a Read tool in the SQL Server MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SQL Server 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 SQL Server MCP Server. Nothing to install.
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 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 SQL Server MCP Server MCP server (nebhg/sql-server-mcp). 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 →