AI agents call text_search_advanced to retrieve information from Postgres Mcp Legacy without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs information retrieval with ranking capabilities. It queries data and returns results ranked by relevance—a classic Read operation with no side effects, data modification, or irreversible actions. The low severity reflects minimal risk: misuse would at worst expose or return incorrect search results, but cannot modify data, execute code, or cause financial impact.
From the tool's definition Tool name is 'text_search_advanced' and description states 'Advanced full-text search with ranking'. Full-text search is a read-only query operation that retrieves and ranks matching data without modifying, deleting, or executing arbitrary code.
Documented attack patterns abuse exactly the kind of access text_search_advanced gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Postgres Mcp Legacy, and nothing reaches the server without passing your rules. This is the rule we recommend for text_search_advanced:
{
"version": "1",
"default": "deny",
"tools": {
"text_search_advanced": {}
}
}text_search_advanced is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Advanced full-text search with ranking. It is categorised as a Read tool in the Postgres Mcp Legacy MCP Server, which means it retrieves data without modifying state.
Register the Postgres Mcp Legacy MCP server in PolicyLayer and add a rule for text_search_advanced: 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 Postgres Mcp Legacy. Nothing to install.
text_search_advanced 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 text_search_advanced 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 text_search_advanced. 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.
text_search_advanced is provided by the Postgres Mcp Legacy MCP server (neverinfamous/postgres-mcp-legacy). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Postgres Mcp Legacy, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
60 Postgres Mcp Legacy tools catalogued and risk-classified — across an index of 43,000+ MCP servers.