# close_position

Close an open position

Agent View of the PolicyLayer registry record for `close_position`. HTML page: https://policylayer.com/tools/8nite-metatrader-4-mcp/close-position

## Facts

- Tool: `close_position`
- 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: Financial (Critical risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Approval-gated

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

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

## Why close_position is rated Critical

Closing a trading position is a financial action that realizes profits or losses, modifies financial exposure, and cannot be undone once executed. This directly commits financial consequences and is irreversible in market terms, placing it in the Financial category with critical severity given the potential for significant monetary impact if misused.

From the tool's own definition: "'close_position' - 'Close an open position' on a MetaTrader 4 trading platform that handles 'order execution'"

## Use case

AI agents use close_position to commit financial operations through MCP MetaTrader 4 Server, usually the final step of a payment, billing, or trading workflow. A call moves real money.

## Recommended policy (PolicyLayer)

Verdict: **Approval-gated**. 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": {
    "close_position": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}
```

## 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
- `place_order` — Financial — https://policylayer.com/tools/8nite-metatrader-4-mcp/place-order.md
- `get_account_info` — Read — https://policylayer.com/tools/8nite-metatrader-4-mcp/get-account-info.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