Analyze time series data with aggregation and trend analysis
AI agents call stats_time_series 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.
This tool performs statistical analysis and aggregation on existing time series data. Analysis operations are read-only queries that retrieve and compute statistics without creating, modifying, deleting, or executing arbitrary operations. The tool fits the Read category as it retrieves or queries data with no side effects.
From the tool's definition Tool name 'stats_time_series' and description 'Analyze time series data with aggregation and trend analysis' indicate data retrieval and analysis operations without modification. Verbs like 'analyze' are passive query operations.
Documented attack patterns abuse exactly the kind of access stats_time_series 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 stats_time_series:
{
"version": "1",
"default": "deny",
"tools": {
"stats_time_series": {}
}
}stats_time_series 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 time series data with aggregation and trend analysis. 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 stats_time_series: 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.
stats_time_series 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 stats_time_series 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 stats_time_series. 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.
stats_time_series 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.