pg_text_search_config
List available full-text search configurations (e.g., english, german, simple).
This record as markdown: /tools/io-github-neverinfamous-postgres-mcp/pg-text-search-config.md
What pg_text_search_config does on PostgreSQL MCP Server
AI agents call pg_text_search_config 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.
Why pg_text_search_config is rated Low
This tool performs a read-only listing of system metadata (available text search configurations). It has no side effects, does not execute code or commands, does not modify data, and does not delete or move resources. The operation is purely informational retrieval, fitting the Read category. Severity is low as misuse would only expose non-sensitive configuration names.
From the tool's definition Tool name and description indicate it 'List available full-text search configurations' — a query operation that retrieves and enumerates existing search configurations without modification or execution.
Attacks that exploit this kind of access
The rule that runs pg_text_search_config 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_config, this is the rule to start with:
pg_text_search_config is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect PostgreSQL MCP Server, apply this rule, and every pg_text_search_config call is checked against it from then on.
Questions about pg_text_search_config
List available full-text search configurations (e.g., english, german, simple). It is categorised as a Read tool in the PostgreSQL MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PostgreSQL MCP Server MCP server in PolicyLayer and add a rule for pg_text_search_config: 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.
pg_text_search_config is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the pg_text_search_config 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.
Set action: deny in the PolicyLayer policy for pg_text_search_config. 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.
pg_text_search_config 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.
This server
Across the catalogue