pg_kcache_top_io
Get top I/O-consuming queries. Shows filesystem-level reads and writes, which represent actual disk access (not just shared buffer hits).
This record as markdown: /tools/io-github-neverinfamous-postgres-mcp/pg-kcache-top-io.md
What pg_kcache_top_io does on PostgreSQL MCP Server
AI agents call pg_kcache_top_io 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_io is rated Low
This tool retrieves and displays performance metrics about query I/O behavior. It performs read-only observation of system statistics and query performance data. The verb 'Get' and the focus on showing/displaying metrics confirms this is a query/reporting function with no side effects on data or system state.
From the tool's definition Tool name 'pg_kcache_top_io' and description 'Get top I/O-consuming queries. Shows filesystem-level reads and writes' indicates a query and reporting function that retrieves diagnostic information about disk I/O patterns without modifying data.
Attacks that exploit this kind of access
The rule that runs pg_kcache_top_io 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_io, this is the rule to start with:
pg_kcache_top_io 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_io call is checked against it from then on.
Questions about pg_kcache_top_io
Get top I/O-consuming queries. Shows filesystem-level reads and writes, which represent actual disk access (not just shared buffer hits). 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_io: 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_io 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_io 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_io. 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_io 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