forecast_models_delete
Preview or permanently delete one stored trained forecast model.
This record as markdown: /tools/emerzon-mt-data-mcp/forecast-models-delete.md
What forecast_models_delete does on MetaTrader5 MCP Server
AI agents call forecast_models_delete to permanently remove resources in MetaTrader5 MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why forecast_models_delete is rated Critical
Irreversibly removes trained models; cannot be undone and causes data loss.
From the tool's definition permanently delete one stored trained forecast model
Attacks that exploit this kind of access
The rule that runs forecast_models_delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MetaTrader5 MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For forecast_models_delete, this is the rule to start with:
forecast_models_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect MetaTrader5 MCP Server, apply this rule, and every forecast_models_delete call is checked against it from then on.
Questions about forecast_models_delete
Preview or permanently delete one stored trained forecast model. It is categorised as a Destructive tool in the MetaTrader5 MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MetaTrader5 MCP Server MCP server in PolicyLayer and add a rule for forecast_models_delete: 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 MetaTrader5 MCP Server. Nothing to install.
forecast_models_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the forecast_models_delete 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 forecast_models_delete. 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.
forecast_models_delete is provided by the MetaTrader5 MCP Server MCP server (emerzon/mt-data-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MetaTrader5 MCP Server, and thousands of servers like it.
Across the catalogue