pg_cache_hit_ratio

Get buffer cache hit ratio statistics.

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-cache-hit-ratio.md

WHAT IT DOES

What pg_cache_hit_ratio does on PostgreSQL MCP Server

AI agents call pg_cache_hit_ratio 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.

RISK

Why pg_cache_hit_ratio is rated Low

This tool retrieves read-only statistics about PostgreSQL's buffer cache performance. It performs no data modification, deletion, code execution, or financial operations. The 'Get' verb and 'statistics' noun confirm it is a passive query operation, consistent with the Read category. Low severity because viewing cache metrics cannot harm the system.

From the tool's definition Tool name 'pg_cache_hit_ratio' and description 'Get buffer cache hit ratio statistics' indicate a retrieval operation that queries performance metrics without modifying data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs pg_cache_hit_ratio 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_cache_hit_ratio, this is the rule to start with:

pg_cache_hit_ratio Allowed

pg_cache_hit_ratio is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pg_cache_hit_ratio": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect PostgreSQL MCP Server, apply this rule, and every pg_cache_hit_ratio call is checked against it from then on.

FAQ

Questions about pg_cache_hit_ratio

What does the pg_cache_hit_ratio tool do? +

Get buffer cache hit ratio statistics. 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_cache_hit_ratio? +

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

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

Can I rate-limit pg_cache_hit_ratio? +

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

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

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

KEEP EXPLORING

What pg_cache_hit_ratio does on PostgreSQL MCP Server

Why pg_cache_hit_ratio is rated Low

The rule that runs pg_cache_hit_ratio safely

Questions about pg_cache_hit_ratio

More on PostgreSQL MCP Server, and thousands of servers like it.