Analyze database growth and project future capacity needs
AI agents call capacity_planning to retrieve information from Postgres Mcp Legacy without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool reads database metrics and generates projections/forecasts. It has no side effects, does not modify configuration or data, does not execute arbitrary operations, and does not delete or move resources. Even if misused by an agent, the worst outcome would be incorrect capacity planning advice. This is a Read category tool with low severity risk.
From the tool's definition Tool performs 'Analyze database growth and project future capacity needs' — a retrospective analysis operation with no modification of data, no code execution, and no destructive actions. This is a query/analytical tool.
Documented attack patterns abuse exactly the kind of access capacity_planning gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Postgres Mcp Legacy, and nothing reaches the server without passing your rules. This is the rule we recommend for capacity_planning:
{
"version": "1",
"default": "deny",
"tools": {
"capacity_planning": {}
}
}capacity_planning 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 and project future capacity needs. It is categorised as a Read tool in the Postgres Mcp Legacy MCP Server, which means it retrieves data without modifying state.
Register the Postgres Mcp Legacy MCP server in PolicyLayer and add a rule for capacity_planning: 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 Mcp Legacy. Nothing to install.
capacity_planning 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 capacity_planning 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 capacity_planning. 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.
capacity_planning is provided by the Postgres Mcp Legacy MCP server (neverinfamous/postgres-mcp-legacy). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Postgres Mcp Legacy, 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.
60 Postgres Mcp Legacy tools catalogued and risk-classified — across an index of 43,000+ MCP servers.