List forecast history with optional filtering by city.
AI agents call list_forecasts to retrieve information from Forecast Storage MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries stored forecast data from the PostgreSQL database. It supports optional filtering but performs no mutations, deletions, or external operations. The blast radius of misuse is minimal—an AI agent listing forecasts cannot cause data loss, execute code, incur financial costs, or modify the database. This is a straightforward Read operation.
From the tool's definition Tool name 'list_forecasts' and description 'List forecast history with optional filtering by city' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
List forecast history with optional filtering by city. It is categorised as a Read tool in the Forecast Storage MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Forecast Storage MCP Server MCP server in PolicyLayer and add a rule for list_forecasts: 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 Forecast Storage MCP Server. Nothing to install.
list_forecasts 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 list_forecasts 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 list_forecasts. 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.
list_forecasts is provided by the Forecast Storage MCP Server MCP server (whut-news/forecast_storage_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →