query_database · Postgres MCP Server MCP: Risk & Policy

WHAT IT DOES

What query_database does on Postgres MCP Server

AI agents invoke query_database to trigger actions in Postgres 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 query_database needs a policy

The tool description says it executes 'a SQL query' with no restriction to SELECT-only statements. While the server description mentions SELECT queries, the tool itself does not enforce this constraint. An AI agent could potentially run INSERT, UPDATE, DELETE, or even DROP statements, making this Execute (with potential Destructive risk).

From the tool's definition 'Execute a SQL query against the PostgreSQL database' — the tool runs arbitrary SQL, not just SELECT statements despite the server description mentioning SELECT queries.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

query_database Rate-limited

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

FAQ

Questions about query_database

What does the query_database tool do? +

Execute a SQL query against the PostgreSQL database. It is categorised as a Execute tool in the Postgres 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 query_database? +

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

What risk level is query_database? +

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

Can I rate-limit query_database? +

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

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

query_database is provided by the Postgres MCP Server MCP server (wongjingping/postgres-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.