pg_ltree_query

Query hierarchical relationships in ltree columns. Supports exact paths (descendants/ancestors) and lquery patterns with wildcards.

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-ltree-query.md

What pg_ltree_query does on PostgreSQL MCP Server

AI agents call pg_ltree_query 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_ltree_query is rated Low

The tool is explicitly a query function that searches for and retrieves hierarchical data using path and pattern matching. No write, delete, execute, or financial operations are described. The 'Query' in the name and 'Query hierarchical relationships' in the description confirm this is a retrieval-only operation with no side effects.

From the tool's definition Tool description states 'Query hierarchical relationships' and 'Supports exact paths (descendants/ancestors) and lquery patterns' — these are read operations that retrieve data matching hierarchical patterns in ltree columns without modifying state.

Questions about pg_ltree_query

What does the pg_ltree_query tool do? +

Query hierarchical relationships in ltree columns. Supports exact paths (descendants/ancestors) and lquery patterns with wildcards. 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_ltree_query? +

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

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

Can I rate-limit pg_ltree_query? +

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

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

pg_ltree_query 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of PostgreSQL MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.