Execute an arbitrary SQL query against the specified database and return the results as a formatted table.
AI agents invoke execute_query to trigger actions in Sql Database. 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 | The SQL query to execute |
server | string | Yes | Server hostname (e.g. server1.database.windows.net) |
database | string | Yes | Database name |
Parameters from the server's own tool schema.
This tool permits execution of any SQL statement supplied by the caller, including potentially destructive operations (DELETE, DROP, TRUNCATE) or data exfiltration queries.
From the tool's definition Tool name 'execute_query' combined with description 'Execute an arbitrary SQL query' indicates execution of arbitrary code. The phrase 'arbitrary SQL query' is explicit that the tool accepts any SQL command without restriction.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
Execute an arbitrary SQL query against the specified database and return the results as a formatted table. It is categorised as a Execute tool in the Sql Database MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
execute_query accepts 3 parameters: query, server, database. Required: query, server, database. The full parameter table on this page comes from the server's own tool schema.
Register the Sql Database 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 Sql Database. 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 Sql Database MCP server (sql-database-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 →