# get_account_info

Get MetaTrader 4 account information

Agent View of the PolicyLayer registry record for `get_account_info`. HTML page: https://policylayer.com/tools/8nite-metatrader-4-mcp/get-account-info

## Facts

- Tool: `get_account_info`
- Server: MCP MetaTrader 4 Server (`8nite/metatrader-4-mcp`) — https://policylayer.com/tools/8nite-metatrader-4-mcp.md
- Homepage: https://github.com/8nite/metatrader-4-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": "get_account_info",
    "arguments": {}
  }
}
```

## Why get_account_info is rated Low

This tool retrieves account metadata (balance, equity, open positions, leverage, etc.) from the MetaTrader 4 platform without creating, modifying, or deleting any data. It is purely informational and poses minimal risk even if misused by an AI agent, as the worst outcome is unauthorized visibility into account details rather than financial loss or destructive action.

From the tool's own definition: "Tool is named 'get_account_info' and described as retrieving MetaTrader 4 account information. The verb 'get' and description indicate data retrieval with no modification or side effects."

## Use case

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

## Recommended policy (PolicyLayer)

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

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

## Other tools on MCP MetaTrader 4 Server (13)

- `compile_ea` — Execute — https://policylayer.com/tools/8nite-metatrader-4-mcp/compile-ea.md
- `run_backtest` — Execute — https://policylayer.com/tools/8nite-metatrader-4-mcp/run-backtest.md
- `close_position` — Financial — https://policylayer.com/tools/8nite-metatrader-4-mcp/close-position.md
- `place_order` — Financial — https://policylayer.com/tools/8nite-metatrader-4-mcp/place-order.md
- `get_backtest_results` — Read — https://policylayer.com/tools/8nite-metatrader-4-mcp/get-backtest-results.md
- `get_backtest_status` — Read — https://policylayer.com/tools/8nite-metatrader-4-mcp/get-backtest-status.md
- `get_history` — Read — https://policylayer.com/tools/8nite-metatrader-4-mcp/get-history.md
- `get_market_data` — Read — https://policylayer.com/tools/8nite-metatrader-4-mcp/get-market-data.md
- `get_positions` — Read — https://policylayer.com/tools/8nite-metatrader-4-mcp/get-positions.md
- `list_experts` — Read — https://policylayer.com/tools/8nite-metatrader-4-mcp/list-experts.md
- `list_local_eas` — Read — https://policylayer.com/tools/8nite-metatrader-4-mcp/list-local-eas.md
- `sync_ea` — Write — https://policylayer.com/tools/8nite-metatrader-4-mcp/sync-ea.md
- `sync_ea_from_file` — Write — https://policylayer.com/tools/8nite-metatrader-4-mcp/sync-ea-from-file.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=8nite-metatrader-4-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/8nite-metatrader-4-mcp