Detect tables with high I/O operations based on statistics.
AI agents call PostgreSQL_high_io_tables to retrieve information from Postgres without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs data retrieval and analysis of PostgreSQL statistics to identify tables with high I/O usage. It reads diagnostic information from the database but does not create, modify, delete, or execute code. The function is purely observational—gathering metrics to support performance tuning decisions. This fits the 'Read' category as a diagnostic query with no side effects.
From the tool's definition Tool name and description: 'Detect tables with high I/O operations based on statistics' — this analyzes existing database statistics to identify problematic tables, with no modification or deletion of data, and no execution of arbitrary commands.
Documented attack patterns abuse exactly the kind of access PostgreSQL_high_io_tables gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Postgres, and nothing reaches the server without passing your rules. This is the rule we recommend for PostgreSQL_high_io_tables:
{
"version": "1",
"default": "deny",
"tools": {
"PostgreSQL_high_io_tables": {}
}
}PostgreSQL_high_io_tables is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Detect tables with high I/O operations based on statistics. It is categorised as a Read tool in the Postgres MCP Server, which means it retrieves data without modifying state.
Register the Postgres MCP server in PolicyLayer and add a rule for PostgreSQL_high_io_tables: 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 Postgres. Nothing to install.
PostgreSQL_high_io_tables 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 PostgreSQL_high_io_tables 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 PostgreSQL_high_io_tables. 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.
PostgreSQL_high_io_tables is provided by the Postgres MCP server (mukul975/postgres-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Postgres, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
239 Postgres tools catalogued and risk-classified — across an index of 43,000+ MCP servers.