podbc_execute_query · MCP PyODBC Server MCP: Risk & Policy

WHAT IT DOES

What podbc_execute_query does on MCP PyODBC Server

AI agents invoke podbc_execute_query to trigger actions in MCP PyODBC 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 podbc_execute_query needs a policy

SQL query execution is a code execution category risk because: (1) it runs code (SQL) whose effects depend entirely on the query argument supplied by the caller; (2) depending on database permissions and query content, it could perform reads, writes, or destructive operations (DELETE, DROP, UPDATE); (3) the tool does not restrict query types, making it capable of triggering unintended side effects.

From the tool's definition Tool name 'podbc_execute_query' combined with description 'Execute a SQL query and return results in JSONL format' explicitly indicates execution of arbitrary SQL queries against a database via ODBC connection.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

podbc_execute_query Rate-limited

podbc_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": {
    "podbc_execute_query": {
      "limits": [
        {
          "counter": "podbc_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 MCP PyODBC Server, so you can run agents against it safely.

FAQ

Questions about podbc_execute_query

What does the podbc_execute_query tool do? +

Execute a SQL query and return results in JSONL format. It is categorised as a Execute tool in the MCP PyODBC 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 podbc_execute_query? +

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

What risk level is podbc_execute_query? +

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

Can I rate-limit podbc_execute_query? +

Yes. Add a rate_limit block to the podbc_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 podbc_execute_query completely? +

Set action: deny in the PolicyLayer policy for podbc_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 podbc_execute_query? +

podbc_execute_query is provided by the MCP PyODBC Server MCP server (openlinksoftware/mcp-pyodbc-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.