# trade_history

A read tool on the MetaTrader5 MCP Server MCP server.

Agent View of the PolicyLayer registry record for `trade_history`. HTML page: https://policylayer.com/tools/emerzon-mt-data-mcp/trade-history

## Facts

- Tool: `trade_history`
- Server: MetaTrader5 MCP Server (`emerzon/mt-data-mcp`) — https://policylayer.com/tools/emerzon-mt-data-mcp.md
- Homepage: https://github.com/emerzon/mt-data-mcp
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "trade_history",
    "arguments": {}
  }
}
```

## Why trade_history is rated Low

The tool name strongly implies querying historical trade records—a read operation with no side effects. While the empty description limits certainty, the server's primary purpose (market data access, technical analysis) and the absence of destructive/financial operation verbs (delete, transfer, execute order) suggest this retrieves data only.

From the tool's own definition: "Tool name 'trade_history' suggests retrieval of past trading records without modification. Description is empty, which reduces confidence."

## Use case

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

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches MetaTrader5 MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "trade_history": {}
  }
}
```

## Other tools on MetaTrader5 MCP Server (81)

- `forecast_models_cleanup` — Destructive — https://policylayer.com/tools/emerzon-mt-data-mcp/forecast-models-cleanup.md
- `forecast_models_delete` — Destructive — https://policylayer.com/tools/emerzon-mt-data-mcp/forecast-models-delete.md
- `forecast_task_cancel` — Destructive — https://policylayer.com/tools/emerzon-mt-data-mcp/forecast-task-cancel.md
- `forecast_task_cancel_all` — Destructive — https://policylayer.com/tools/emerzon-mt-data-mcp/forecast-task-cancel-all.md
- `forecast_backtest_run` — Execute — https://policylayer.com/tools/emerzon-mt-data-mcp/forecast-backtest-run.md
- `forecast_generate` — Execute — https://policylayer.com/tools/emerzon-mt-data-mcp/forecast-generate.md
- `forecast_task_wait` — Execute — https://policylayer.com/tools/emerzon-mt-data-mcp/forecast-task-wait.md
- `forecast_train` — Execute — https://policylayer.com/tools/emerzon-mt-data-mcp/forecast-train.md
- `forecast_tune_genetic` — Execute — https://policylayer.com/tools/emerzon-mt-data-mcp/forecast-tune-genetic.md
- `forecast_tune_optuna` — Execute — https://policylayer.com/tools/emerzon-mt-data-mcp/forecast-tune-optuna.md
- `options_heston_calibrate` — Execute — https://policylayer.com/tools/emerzon-mt-data-mcp/options-heston-calibrate.md
- `strategy_backtest` — Execute — https://policylayer.com/tools/emerzon-mt-data-mcp/strategy-backtest.md
- `strategy_validate` — Execute — https://policylayer.com/tools/emerzon-mt-data-mcp/strategy-validate.md
- `wait_event` — Execute — https://policylayer.com/tools/emerzon-mt-data-mcp/wait-event.md
- `forecast_barrier_optimize` — Financial — https://policylayer.com/tools/emerzon-mt-data-mcp/forecast-barrier-optimize.md
- `options_barrier_price` — Financial — https://policylayer.com/tools/emerzon-mt-data-mcp/options-barrier-price.md
- `trade_close` — Financial — https://policylayer.com/tools/emerzon-mt-data-mcp/trade-close.md
- `trade_modify` — Financial — https://policylayer.com/tools/emerzon-mt-data-mcp/trade-modify.md
- `trade_place` — Financial — https://policylayer.com/tools/emerzon-mt-data-mcp/trade-place.md
- `trade_risk_analyze` — Financial — https://policylayer.com/tools/emerzon-mt-data-mcp/trade-risk-analyze.md
- `trade_var_cvar_calculate` — Financial — https://policylayer.com/tools/emerzon-mt-data-mcp/trade-var-cvar-calculate.md
- `causal_discover_signals` — Other — https://policylayer.com/tools/emerzon-mt-data-mcp/causal-discover-signals.md
- `forecast_barrier_prob` — Other — https://policylayer.com/tools/emerzon-mt-data-mcp/forecast-barrier-prob.md
- `forecast_optimize_hints` — Other — https://policylayer.com/tools/emerzon-mt-data-mcp/forecast-optimize-hints.md
- `labels_triple_barrier` — Other — https://policylayer.com/tools/emerzon-mt-data-mcp/labels-triple-barrier.md
- `report_generate` — Other — https://policylayer.com/tools/emerzon-mt-data-mcp/report-generate.md
- `temporal_analyze` — Other — https://policylayer.com/tools/emerzon-mt-data-mcp/temporal-analyze.md
- `trade_session_context` — Other — https://policylayer.com/tools/emerzon-mt-data-mcp/trade-session-context.md
- `asset_performance` — Read — https://policylayer.com/tools/emerzon-mt-data-mcp/asset-performance.md
- `cointegration_test` — Read — https://policylayer.com/tools/emerzon-mt-data-mcp/cointegration-test.md
- …and 51 more: https://policylayer.com/tools/emerzon-mt-data-mcp.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=emerzon-mt-data-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/emerzon-mt-data-mcp