pg_read_query

Execute a read-only SQL query (SELECT, WITH). Returns rows as JSON. Pass transactionId to execute within a transaction.

SERVERPostgreSQL MCP Server SOURCE@neverinfamous/postgres-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-neverinfamous-postgres-mcp/pg-read-query.md

WHAT IT DOES

What pg_read_query does on PostgreSQL MCP Server

AI agents call pg_read_query to retrieve information from PostgreSQL MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why pg_read_query is rated Low

This tool retrieves data via read-only SQL queries with no side effects. It cannot create, modify, delete data, or execute arbitrary code. The only risk is information disclosure if sensitive data is queried, but that depends on access controls and query construction, not the tool itself.

From the tool's definition Tool name 'pg_read_query' and description explicitly states 'Execute a read-only SQL query (SELECT, WITH). Returns rows as JSON.' The restriction to SELECT and WITH clauses confirms no data modification, deletion, or code execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs pg_read_query safely

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

pg_read_query Allowed

pg_read_query is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pg_read_query": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect PostgreSQL MCP Server, apply this rule, and every pg_read_query call is checked against it from then on.

FAQ

Questions about pg_read_query

What does the pg_read_query tool do? +

Execute a read-only SQL query (SELECT, WITH). Returns rows as JSON. Pass transactionId to execute within a transaction. It is categorised as a Read tool in the PostgreSQL MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on pg_read_query? +

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

What risk level is pg_read_query? +

pg_read_query is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit pg_read_query? +

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

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

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

KEEP EXPLORING

What pg_read_query does on PostgreSQL MCP Server

Why pg_read_query is rated Low

The rule that runs pg_read_query safely

Questions about pg_read_query

More on PostgreSQL MCP Server, and thousands of servers like it.