pg_doc_remove

Remove documents matching a filter from a collection.

SERVERPostgreSQL MCP Server SOURCE@neverinfamous/postgres-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What pg_doc_remove does on PostgreSQL MCP Server

AI agents call pg_doc_remove to permanently remove resources in PostgreSQL MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why pg_doc_remove is rated Critical

This tool irreversibly deletes documents from a collection based on filter criteria. Document removal is a destructive operation that cannot be reversed without a backup restore. The use of a filter parameter creates blast radius risk if an AI agent constructs an overly broad filter (e.g., removing all documents instead of a subset).

From the tool's definition Tool name is 'pg_doc_remove' and description states 'Remove documents matching a filter from a collection.' The verb 'remove' combined with 'matching a filter' indicates bulk deletion of data that cannot be undone.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

pg_doc_remove Hidden

pg_doc_remove is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "pg_doc_remove"
  ]
}

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

FAQ

Questions about pg_doc_remove

What does the pg_doc_remove tool do? +

Remove documents matching a filter from a collection. It is categorised as a Destructive tool in the PostgreSQL MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on pg_doc_remove? +

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

pg_doc_remove is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit pg_doc_remove? +

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

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

pg_doc_remove 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_remove does on PostgreSQL MCP Server

Why pg_doc_remove is rated Critical

The rule that runs pg_doc_remove safely

Questions about pg_doc_remove

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