pg_text_normalize

Remove accent marks (diacritics) from text using PostgreSQL unaccent extension. Note: Does NOT lowercase or trim—use LOWER()/TRIM() in a query for those operations.

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-text-normalize.md

WHAT IT DOES

What pg_text_normalize does on PostgreSQL MCP Server

AI agents call pg_text_normalize 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_text_normalize is rated Critical

An AI agent that decides to call pg_text_normalize doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from PostgreSQL MCP Server is gone. There is no undo for destructive operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

pg_text_normalize Hidden

pg_text_normalize 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_text_normalize"
  ]
}

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

FAQ

Questions about pg_text_normalize

What does the pg_text_normalize tool do? +

Remove accent marks (diacritics) from text using PostgreSQL unaccent extension. Note: Does NOT lowercase or trim—use LOWER()/TRIM() in a query for those operations. 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_text_normalize? +

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

pg_text_normalize 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_text_normalize? +

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

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

pg_text_normalize 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_text_normalize does on PostgreSQL MCP Server

Why pg_text_normalize is rated Critical

The rule that runs pg_text_normalize safely

Questions about pg_text_normalize

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