pg_vector_aggregate
Calculate average vector. Requires: table, column. Optional: groupBy, where.
This record as markdown: /tools/io-github-neverinfamous-postgres-mcp/pg-vector-aggregate.md
What pg_vector_aggregate does on PostgreSQL MCP Server
AI agents call pg_vector_aggregate 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_vector_aggregate is rated Low
This tool performs a statistical aggregation (averaging) on vector data within a PostgreSQL table. It retrieves and computes values based on specified criteria but does not create, modify, delete, or execute external operations. The optional groupBy and where parameters are standard read-query filters. This is a classic Read operation—querying and aggregating existing data with no side effects.
From the tool's definition Tool description states 'Calculate average vector' with parameters for table, column, groupBy, and where clause. The verb 'calculate' and 'average' indicate a query/aggregation operation that retrieves computed data without modification.
Attacks that exploit this kind of access
The rule that runs pg_vector_aggregate 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_vector_aggregate, this is the rule to start with:
pg_vector_aggregate 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_vector_aggregate call is checked against it from then on.
Questions about pg_vector_aggregate
Calculate average vector. Requires: table, column. Optional: groupBy, where. 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_vector_aggregate: 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_vector_aggregate 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_vector_aggregate 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_vector_aggregate. 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_vector_aggregate 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