pg_upsert

Insert a row or update if it already exists (INSERT ... ON CONFLICT DO UPDATE). Specify conflict columns for uniqueness check. Use data or values for column-value pairs.

SERVERPostgreSQL MCP Server SOURCE@neverinfamous/postgres-mcp
Medium RISK CLASS
Category Write
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-neverinfamous-postgres-mcp/pg-upsert.md

What pg_upsert does on PostgreSQL MCP Server

AI agents use pg_upsert to create or update resources in PostgreSQL MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PostgreSQL MCP Server environment.

Why pg_upsert is rated Medium

This tool modifies database state by inserting new rows or updating existing ones based on conflict detection. While reversible (can be undone with subsequent operations or transaction rollback), it permanently alters data once committed. It does not delete, execute arbitrary code, or move money, so Write is the appropriate category.

From the tool's definition Tool performs 'INSERT ... ON CONFLICT DO UPDATE', which creates or modifies data reversibly. Description explicitly states 'Insert a row or update if it already exists', confirming write semantics.

Questions about pg_upsert

What does the pg_upsert tool do? +

Insert a row or update if it already exists (INSERT ... ON CONFLICT DO UPDATE). Specify conflict columns for uniqueness check. Use data or values for column-value pairs. It is categorised as a Write tool in the PostgreSQL MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on pg_upsert? +

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

pg_upsert is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit pg_upsert? +

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

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

pg_upsert 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.

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

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of PostgreSQL MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.