pg_doc_find

Query documents in a JSONB collection with optional filter, field projection, and pagination.

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-doc-find.md

WHAT IT DOES

What pg_doc_find does on PostgreSQL MCP Server

AI agents call pg_doc_find 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_doc_find is rated Low

This tool performs data retrieval operations (query, filter, project, paginate) on stored documents. It has no capability to create, modify, delete, or execute external operations. The scope is limited to reading existing JSONB data with optional filtering and pagination, making it a straightforward Read category tool with low severity risk.

From the tool's definition Tool description states 'Query documents in a JSONB collection with optional filter, field projection, and pagination' — operations that retrieve and filter data without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs pg_doc_find 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_doc_find, this is the rule to start with:

pg_doc_find Allowed

pg_doc_find 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_doc_find": {}
  }
}

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_doc_find call is checked against it from then on.

FAQ

Questions about pg_doc_find

What does the pg_doc_find tool do? +

Query documents in a JSONB collection with optional filter, field projection, and pagination. 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_doc_find? +

Register the PostgreSQL MCP Server MCP server in PolicyLayer and add a rule for pg_doc_find: 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_doc_find? +

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

Can I rate-limit pg_doc_find? +

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

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

pg_doc_find 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_doc_find does on PostgreSQL MCP Server

Why pg_doc_find is rated Low

The rule that runs pg_doc_find safely

Questions about pg_doc_find

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