podbc_query_database · MCP PyODBC Server MCP: Risk & Policy

WHAT IT DOES

What podbc_query_database does on MCP PyODBC Server

AI agents invoke podbc_query_database 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_query_database needs a policy

This tool executes arbitrary SQL queries against a database. Depending on the query content, it could perform reads, writes, or destructive operations (DROP, DELETE, TRUNCATE). Since it accepts arbitrary SQL, it must be classified at the most severe applicable level for an execution context. An AI agent could issue destructive or data-exfiltrating queries, making the blast radius critical.

From the tool's definition "Execute a SQL query" — runs arbitrary SQL against a database via ODBC

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

podbc_query_database Rate-limited

podbc_query_database 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_query_database": {
      "limits": [
        {
          "counter": "podbc_query_database_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_query_database

What does the podbc_query_database 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_query_database? +

Register the MCP PyODBC Server MCP server in PolicyLayer and add a rule for podbc_query_database: 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_query_database? +

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

Can I rate-limit podbc_query_database? +

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

Set action: deny in the PolicyLayer policy for podbc_query_database. 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_query_database? +

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