estimate_query_risk

Estimate deterministic risk score and level for candidate SQL (alias of validate_sql).

Server MSSQL MCP Server mortada7-11/mssql-mcpo-server
Category Read
Risk class Low
Parameters 00 required

What estimate_query_risk does on MSSQL MCP Server

AI agents call estimate_query_risk to retrieve information from MSSQL MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why estimate_query_risk needs a policy

This tool analyzes and scores SQL queries for risk but does not execute them or modify data. It performs a read-like operation (inspection/validation of query text) with no side effects. The server itself emphasizes 'read-only query execution' and 'safety validation', and this tool appears to be part of the validation/safety layer rather than an execution mechanism.

From the tool's definition Tool is an alias of validate_sql which validates SQL syntax and safety. The description states it 'estimate[s] deterministic risk score and level' for candidate SQL, indicating analysis and classification of queries rather than execution.

Questions about estimate_query_risk

What does the estimate_query_risk tool do? +

Estimate deterministic risk score and level for candidate SQL (alias of validate_sql). It is categorised as a Read tool in the MSSQL MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on estimate_query_risk? +

Register the MSSQL MCP Server MCP server in PolicyLayer and add a rule for estimate_query_risk: 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 MSSQL MCP Server. Nothing to install.

What risk level is estimate_query_risk? +

estimate_query_risk is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit estimate_query_risk? +

Yes. Add a rate_limit block to the estimate_query_risk 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.

How do I block estimate_query_risk completely? +

Set action: deny in the PolicyLayer policy for estimate_query_risk. 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.

What MCP server provides estimate_query_risk? +

estimate_query_risk is provided by the MSSQL MCP Server MCP server (mortada7-11/mssql-mcpo-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.