pg_truncate

Truncate a table, removing all rows quickly. Use cascade to truncate dependent tables.

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-truncate.md

What pg_truncate does on PostgreSQL MCP Server

AI agents call pg_truncate 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.

Why pg_truncate is rated Critical

TRUNCATE is a DDL operation that irreversibly deletes all data in a table (and optionally related tables via CASCADE). Unlike DELETE, it cannot be easily rolled back in all contexts and results in permanent data loss.

From the tool's definition Tool name 'pg_truncate' and description states it removes 'all rows quickly' from a table, which is irreversible data deletion. The ability to use 'cascade' to truncate dependent tables amplifies the destructive scope.

Questions about pg_truncate

What does the pg_truncate tool do? +

Truncate a table, removing all rows quickly. Use cascade to truncate dependent tables. 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_truncate? +

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

pg_truncate 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_truncate? +

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

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

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

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