pg_kcache_top_cpu
Get top CPU-consuming queries. Shows which queries spend the most time in user CPU (application code) vs system CPU (kernel operations).
This record as markdown: /tools/io-github-neverinfamous-postgres-mcp/pg-kcache-top-cpu.md
What pg_kcache_top_cpu does on PostgreSQL MCP Server
AI agents call pg_kcache_top_cpu 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_top_cpu is rated Low
This tool retrieves and displays performance monitoring data about CPU usage of existing queries. It is a read-only diagnostic operation with no side effects on the database state or operations. The low severity reflects that query profiling data exposure has minimal security blast radius compared to tools that execute code or modify data.
From the tool's definition Tool name 'pg_kcache_top_cpu' and description 'Get top CPU-consuming queries. Shows which queries spend the most time in user CPU (application code) vs system CPU (kernel operations).' indicate a retrieval operation that queries performance metrics without…
Attacks that exploit this kind of access
The rule that runs pg_kcache_top_cpu 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_kcache_top_cpu, this is the rule to start with:
pg_kcache_top_cpu 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_kcache_top_cpu call is checked against it from then on.
Questions about pg_kcache_top_cpu
Get top CPU-consuming queries. Shows which queries spend the most time in user CPU (application code) vs system CPU (kernel operations). 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_kcache_top_cpu: 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_kcache_top_cpu 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_kcache_top_cpu 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_kcache_top_cpu. 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_kcache_top_cpu 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