cleanup_expired_forecasts

Remove expired forecasts from Cloud SQL database.

Server Forecast Storage MCP Server whut-news/forecast_storage_mcp
Category Destructive
Risk class Critical
Parameters 00 required

What cleanup_expired_forecasts does on Forecast Storage MCP Server

AI agents call cleanup_expired_forecasts to permanently remove resources in Forecast Storage MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why cleanup_expired_forecasts needs a policy

The tool permanently deletes forecasts from Cloud SQL PostgreSQL without reversibility. Although the deletions are scoped to expired records (mitigating uncontrolled blast radius), the operation is fundamentally destructive and cannot be undone. This ranks above Execute because the data loss is irreversible and the tool's primary purpose is deletion, not dynamic execution with variable outcomes.

From the tool's definition Tool name 'cleanup_expired_forecasts' and description 'Remove expired forecasts from Cloud SQL database' indicate irreversible deletion of data records from a persistent database.

Questions about cleanup_expired_forecasts

What does the cleanup_expired_forecasts tool do? +

Remove expired forecasts from Cloud SQL database. It is categorised as a Destructive tool in the Forecast Storage MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on cleanup_expired_forecasts? +

Register the Forecast Storage MCP Server MCP server in PolicyLayer and add a rule for cleanup_expired_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.

What risk level is cleanup_expired_forecasts? +

cleanup_expired_forecasts is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit cleanup_expired_forecasts? +

Yes. Add a rate_limit block to the cleanup_expired_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.

How do I block cleanup_expired_forecasts completely? +

Set action: deny in the PolicyLayer policy for cleanup_expired_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.

What MCP server provides cleanup_expired_forecasts? +

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.