psql-query

Executes a PostgreSQL query via psql and returns structured tabular output.

SERVERBuild SOURCEDave-London/Pare

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dave-london-build/psql-query.md

WHAT IT DOES

What psql-query does on Build

AI agents invoke psql-query to trigger actions in Build. 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.

RISK

Why psql-query is rated High

The tool runs arbitrary SQL queries against a PostgreSQL database. While described generically as 'query', it executes arbitrary SQL which could include DDL (DROP, DELETE, TRUNCATE) or DML statements. The execution of arbitrary database commands makes this Execute at minimum, with potential for Destructive operations depending on the query content.

From the tool's definition Executes a PostgreSQL query via psql

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs psql-query safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Build, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For psql-query, this is the rule to start with:

psql-query Rate-limited

psql-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": {
    "psql-query": {
      "limits": [
        {
          "counter": "psql-query_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Build, apply this rule, and every psql-query call is checked against it from then on.

FAQ

Questions about psql-query

What does the psql-query tool do? +

Executes a PostgreSQL query via psql and returns structured tabular output. It is categorised as a Execute tool in the Build MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

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

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

What risk level is psql-query? +

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

Can I rate-limit psql-query? +

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

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

psql-query is provided by the Build MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Build, and thousands of servers like it.

This server

All 202 Build tools → High-risk tools on this server →

Across the catalogue

aroflo_query_zone on AroFlo MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →