forecast_task_cancel

Cancel a running forecast training task.

SERVERMetaTrader5 MCP Server SOURCEemerzon/mt-data-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/emerzon-mt-data-mcp/forecast-task-cancel.md

WHAT IT DOES

What forecast_task_cancel does on MetaTrader5 MCP Server

AI agents call forecast_task_cancel 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.

RISK

Why forecast_task_cancel is rated Critical

Cancelling a running task is an irreversible action — the in-progress training computation is terminated and its partial results are lost. This cannot be undone (the task cannot be 'un-cancelled'). Severity is medium because it affects a computational task rather than financial data or money movement, but misuse by an AI agent could disrupt important forecasting pipelines.

From the tool's definition Cancel a running forecast training task

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs forecast_task_cancel 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_task_cancel, this is the rule to start with:

forecast_task_cancel Hidden

forecast_task_cancel is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "forecast_task_cancel"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect MetaTrader5 MCP Server, apply this rule, and every forecast_task_cancel call is checked against it from then on.

FAQ

Questions about forecast_task_cancel

What does the forecast_task_cancel tool do? +

Cancel a running forecast training task. 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.

How do I enforce a policy on forecast_task_cancel? +

Register the MetaTrader5 MCP Server MCP server in PolicyLayer and add a rule for forecast_task_cancel: 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.

What risk level is forecast_task_cancel? +

forecast_task_cancel 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 forecast_task_cancel? +

Yes. Add a rate_limit block to the forecast_task_cancel 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 forecast_task_cancel completely? +

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

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

KEEP EXPLORING

More on MetaTrader5 MCP Server, and thousands of servers like it.

This server

All 82 MetaTrader5 MCP Server tools → Critical-risk tools on this server →

Across the catalogue

sms_cancel_scheduled on Twilio SMS MCP Server →cancel_all_orders on Lighter MCP →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →