pg_kcache_query_stats

Get query statistics with OS-level CPU and I/O metrics. Joins pg_stat_statements with pg_stat_kcache to show what SQL did AND what system resources it consumed. orderBy options:

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-kcache-query-stats.md

What pg_kcache_query_stats does on PostgreSQL MCP Server

AI agents call pg_kcache_query_stats 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_kcache_query_stats is rated Low

This tool performs a read-only query operation to gather diagnostic and performance metrics about previously executed queries. It has no side effects, creates no modifications to data, and poses minimal risk even if an AI agent invokes it with arbitrary orderBy parameters. The worst case would be returning unexpected metric ordering, not data loss or system compromise.

From the tool's definition Tool description states 'Get query statistics' and 'show what SQL did AND what system resources it consumed' — these are retrieval operations.

Questions about pg_kcache_query_stats

What does the pg_kcache_query_stats tool do? +

Get query statistics with OS-level CPU and I/O metrics. Joins pg_stat_statements with pg_stat_kcache to show what SQL did AND what system resources it consumed. orderBy options:. 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_kcache_query_stats? +

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

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

Can I rate-limit pg_kcache_query_stats? +

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

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

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