Analyze database growth patterns and forecast disk usage.
AI agents call PostgreSQL_disk_usage_forecast 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.
The tool performs forecasting and analysis on database metrics (growth patterns, disk usage), which are Read operations. It retrieves and interprets existing monitoring data to generate predictions. No data is modified, deleted, or executed. The sibling tools (analyze_* variants) confirm this server provides diagnostic/analytical capabilities.
From the tool's definition Tool description states 'Analyze database growth patterns and forecast disk usage' — this is an analytical/diagnostic operation that retrieves and examines existing data without modification, deletion, or execution of arbitrary code.
Documented attack patterns abuse exactly the kind of access PostgreSQL_disk_usage_forecast 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_disk_usage_forecast:
{
"version": "1",
"default": "deny",
"tools": {
"PostgreSQL_disk_usage_forecast": {}
}
}PostgreSQL_disk_usage_forecast 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.
Analyze database growth patterns and forecast disk usage. 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_disk_usage_forecast: 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_disk_usage_forecast 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_disk_usage_forecast 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_disk_usage_forecast. 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_disk_usage_forecast 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.