pg_text_search

Full-text search using tsvector and tsquery.

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

WHAT IT DOES

What pg_text_search does on PostgreSQL MCP Server

AI agents call pg_text_search 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_text_search is rated Low

Full-text search is a query operation that searches through indexed text data and returns matching results. It has no side effects, does not modify data, and does not execute arbitrary code or trigger destructive operations. This is a straightforward Read category tool with low severity since the blast radius of misuse is limited to unauthorized data exposure.

From the tool's definition Tool name is 'pg_text_search' and description states 'Full-text search using tsvector and tsquery.' Full-text search in PostgreSQL using tsvector and tsquery are read-only operations that query and retrieve matching text data without modifying or deleting any…

Attacks that exploit this kind of access

RECOMMENDED RULE

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

pg_text_search Allowed

pg_text_search 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_text_search": {}
  }
}

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

FAQ

Questions about pg_text_search

What does the pg_text_search tool do? +

Full-text search using tsvector and tsquery. 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_text_search? +

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

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

Can I rate-limit pg_text_search? +

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

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

pg_text_search 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_search does on PostgreSQL MCP Server

Why pg_text_search is rated Low

The rule that runs pg_text_search safely

Questions about pg_text_search

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