pg_like_search

Search text using LIKE patterns. Case-insensitive (ILIKE) by default.

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

WHAT IT DOES

What pg_like_search does on PostgreSQL MCP Server

AI agents call pg_like_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_like_search is rated Low

This tool retrieves or queries data using LIKE pattern matching, which is a read-only operation with no side effects. It does not create, modify, delete, or execute code. The case-insensitive search capability (ILIKE) is still a passive retrieval operation. Even if misused by an AI agent, it can only expose existing data, not modify or destroy it.

From the tool's definition Tool description states 'Search text using LIKE patterns' with no mention of data modification, deletion, or execution of arbitrary operations. The function is explicitly a search/query operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

pg_like_search Allowed

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

FAQ

Questions about pg_like_search

What does the pg_like_search tool do? +

Search text using LIKE patterns. Case-insensitive (ILIKE) by default. 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_like_search? +

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

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

Can I rate-limit pg_like_search? +

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

Set action: deny in the PolicyLayer policy for pg_like_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_like_search? +

pg_like_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_like_search does on PostgreSQL MCP Server

Why pg_like_search is rated Low

The rule that runs pg_like_search safely

Questions about pg_like_search

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