pg_kcache_resource_analysis
Analyze queries to classify them as CPU-bound, I/O-bound, or balanced. Helps identify the root cause of performance issues - is the query computation-heavy or disk-heavy?
This record as markdown: /tools/io-github-neverinfamous-postgres-mcp/pg-kcache-resource-analysis.md
What pg_kcache_resource_analysis does on PostgreSQL MCP Server
AI agents call pg_kcache_resource_analysis 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_resource_analysis is rated Low
The tool performs analysis and classification of query resource usage patterns (CPU-bound, I/O-bound, or balanced) to help diagnose performance bottlenecks. This is purely informational—it retrieves and interprets diagnostic metadata without creating, modifying, deleting, or executing any operations that change database state or trigger external actions. It falls squarely within the Read category.
From the tool's definition Tool name 'pg_kcache_resource_analysis' and description state it 'Analyze queries to classify them' — this is a query analysis and classification operation with no side effects on data or system state.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs pg_kcache_resource_analysis 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_resource_analysis, this is the rule to start with:
pg_kcache_resource_analysis 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_resource_analysis call is checked against it from then on.
Questions about pg_kcache_resource_analysis
Analyze queries to classify them as CPU-bound, I/O-bound, or balanced. Helps identify the root cause of performance issues - is the query computation-heavy or disk-heavy?. 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_resource_analysis: 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_resource_analysis 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_resource_analysis 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_resource_analysis. 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_resource_analysis 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