run_postgres_query · MCP Server MCP: Risk & Policy

WHAT IT DOES

What run_postgres_query does on MCP Server

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

Although this could span both Execute and Destructive categories, the description does not explicitly restrict the types of SQL queries allowed. An AI agent with access to this tool could execute any arbitrary SQL statement.

From the tool's definition Tool name is 'run_postgres_query' with description 'Run a SQL query against the PostgreSQL database.' The ability to 'run a SQL query' without restrictions means arbitrary SQL execution, including potential destructive operations (DELETE, DROP, UPDATE) or…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_postgres_query Rate-limited

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

FAQ

Questions about run_postgres_query

What does the run_postgres_query tool do? +

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

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

What risk level is run_postgres_query? +

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

Can I rate-limit run_postgres_query? +

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

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

run_postgres_query is provided by the MCP Server MCP server (namto908/mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.