get_backtest_status

Get the current status of a running backtest

SERVERMCP MetaTrader 4 Server SOURCE8nite/metatrader-4-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/8nite-metatrader-4-mcp/get-backtest-status.md

WHAT IT DOES

What get_backtest_status does on MCP MetaTrader 4 Server

AI agents call get_backtest_status to retrieve information from MCP MetaTrader 4 Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_backtest_status is rated Low

This tool queries the status of an existing backtest process without modifying, executing, or destroying any data. It is a simple read operation that returns current state information. The low severity reflects that status checks cannot be misused to cause financial loss, data destruction, or code execution—they only retrieve information about ongoing operations.

From the tool's definition Tool name 'get_backtest_status' and description 'Get the current status of a running backtest' indicate a retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_backtest_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and MCP MetaTrader 4 Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_backtest_status, this is the rule to start with:

get_backtest_status Allowed

get_backtest_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_backtest_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about get_backtest_status

What does the get_backtest_status tool do? +

Get the current status of a running backtest. It is categorised as a Read tool in the MCP MetaTrader 4 Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_backtest_status? +

Register the MCP MetaTrader 4 Server MCP server in PolicyLayer and add a rule for get_backtest_status: 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 MCP MetaTrader 4 Server. Nothing to install.

What risk level is get_backtest_status? +

get_backtest_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_backtest_status? +

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

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

get_backtest_status is provided by the MCP MetaTrader 4 Server MCP server (8nite/metatrader-4-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

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

This server

All 14 MCP MetaTrader 4 Server tools →

Across the catalogue

get_task_status on 0rca Dojo MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →