AI agents invoke execute_query to trigger actions in Mssql. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | Yes | SQL SELECT query to execute |
connectionName | string | — | Named connection to use (e.g., 'production', 'staging') |
connectionString | string | — | SQL Server connection string (uses default if not provided) |
Parameters from the server's own tool schema.
The tool executes arbitrary SQL queries supplied by the user ('custom SQL'). While limited to SELECT in the description, the Execute category applies because: (1) the tool runs code whose effects depend on the query argument, (2) it accesses database state in ways that could have side effects or inform privileged operations, and (3) in the context of a comprehensive SQL server MCP with stored procedure access, this…
From the tool's definition Tool name is 'execute_query' and description states it 'Execute[s] a custom SQL SELECT query'. The word 'Execute' combined with 'custom' SQL indicates arbitrary code execution capability.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
Execute a custom SQL SELECT query with automatic limit (top 20 rows). It is categorised as a Execute tool in the Mssql MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
execute_query accepts 3 parameters: query, connectionName, connectionString. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Mssql MCP server in PolicyLayer and add a rule for execute_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 Mssql. Nothing to install.
execute_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 execute_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 execute_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.
execute_query is provided by the Mssql MCP server (mssql-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 →