execute-query · ODBC MCP Server MCP: Risk & Policy

WHAT IT DOES

What execute-query does on ODBC MCP Server

AI agents invoke execute-query to trigger actions in ODBC MCP Server. 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.

WHY IT NEEDS A POLICY

Why execute-query needs a policy

This tool executes arbitrary SQL queries, which qualifies as Execute rather than Read. Although the server claims read-only protections, the tool description does not explicitly confirm those restrictions are enforced at the tool level, and SQL execution carries significant risk if those safeguards fail or are bypassed.

From the tool's definition Tool name 'execute-query' and description 'Execute an SQL query and return results' indicate execution of arbitrary SQL statements.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute-query Rate-limited

execute-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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "execute-query": {
      "limits": [
        {
          "counter": "execute-query_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches ODBC MCP Server, so you can run agents against it safely.

FAQ

Questions about execute-query

What does the execute-query tool do? +

Execute an SQL query and return results. It is categorised as a Execute tool in the ODBC MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on execute-query? +

Register the ODBC MCP Server 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 ODBC MCP Server. Nothing to install.

What risk level is execute-query? +

execute-query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit execute-query? +

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.

How do I block execute-query completely? +

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.

What MCP server provides execute-query? +

execute-query is provided by the ODBC MCP Server MCP server (tylerstoltz/mcp-odbc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.