Execute a SQL query directly on the database
AI agents invoke execute_sql_query to trigger actions in SQLGenius. 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.
SQL query execution is Execute category because it can trigger arbitrary database operations (SELECT, INSERT, UPDATE, DELETE, etc.) depending on what query is passed to it. The severity is high because a malicious or erroneous query could modify or delete significant data, though without explicit evidence that DELETE/DROP operations are permitted, it is not classified as Destructive.
From the tool's definition Tool description states 'Execute a SQL query directly on the database' - the verb 'Execute' combined with 'directly on the database' indicates the tool runs arbitrary SQL queries whose effects depend on the query arguments.
Documented attack patterns abuse exactly the kind of access execute_sql_query gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SQLGenius, and nothing reaches the server without passing your rules. This is the rule we recommend for execute_sql_query:
{
"version": "1",
"default": "deny",
"tools": {
"execute_sql_query": {
"limits": [
{
"counter": "execute_sql_query_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}execute_sql_query stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Execute a SQL query directly on the database. It is categorised as a Execute tool in the SQLGenius MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the SQLGenius MCP server in PolicyLayer and add a rule for execute_sql_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 SQLGenius. Nothing to install.
execute_sql_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_sql_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_sql_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_sql_query is provided by the SQLGenius MCP server (pawankumar94/sql_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SQLGenius, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 SQLGenius tools catalogued and risk-classified — across an index of 43,000+ MCP servers.