# mw_read_load_order

Post your load order — but here, not in a Discord. Reads it for a specific game from whichever manager the user runs (MO2, r2modman, or best-effort Vortex). Normalized output: each entry has name, enabled state, load-order index, and attribution when available. Read-only. Use when the user says "show/post my load order", "what mods do I have enabled", or "what order are my mods in".

Agent View of the PolicyLayer registry record for `mw_read_load_order`. HTML page: https://policylayer.com/tools/171county-modwrench/mw-read-load-order

## Facts

- Tool: `mw_read_load_order`
- Server: ModWrench MCP Server (`@modwrench/cli`) — https://policylayer.com/tools/171county-modwrench.md
- Install: `npx -y @modwrench/cli`
- Homepage: https://github.com/171county/modwrench
- Risk category: Read (Low risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 4 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `gameId` | string | yes | Canonical game ID (e.g. 'skyrimspecialedition', 'lethalcompany'). Use mw_detect_environment to discover the games on this machine. |
| `modManager` | string | no | Which mod manager to read from. Default 'auto' — picks the most likely manager for this game's family. |
| `profileName` | string | no | Profile name. MO2 reads the active profile from ModOrganizer.ini if omitted; r2modman defaults to the first profile alphabetically (typically 'Default'). |
| `instancePath` | string | no | Optional override for MO2's instance path — useful for portable MO2 installs that don't live under %LOCALAPPDATA%/ModOrganizer. |

Parameters from the server's own tool schema.

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

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "mw_read_load_order",
    "arguments": {
      "gameId": "<gameId>"
    }
  }
}
```

## Why mw_read_load_order is rated Low

Even though mw_read_load_order only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

## Use case

AI agents call mw_read_load_order to retrieve information from ModWrench 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 ModWrench MCP Server:

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

## Other tools on ModWrench MCP Server (16)

- `mw_parse_crashlog` — Execute — https://policylayer.com/tools/171county-modwrench/mw-parse-crashlog.md
- `thunderstore_mod_dependencies` — Execute — https://policylayer.com/tools/171county-modwrench/thunderstore-mod-dependencies.md
- `mw_check_known_conflicts` — Read — https://policylayer.com/tools/171county-modwrench/mw-check-known-conflicts.md
- `mw_detect_environment` — Read — https://policylayer.com/tools/171county-modwrench/mw-detect-environment.md
- `mw_diagnose_crash` — Read — https://policylayer.com/tools/171county-modwrench/mw-diagnose-crash.md
- `mw_query_mod_metadata` — Read — https://policylayer.com/tools/171county-modwrench/mw-query-mod-metadata.md
- `thunderstore_get_community` — Read — https://policylayer.com/tools/171county-modwrench/thunderstore-get-community.md
- `thunderstore_get_mod` — Read — https://policylayer.com/tools/171county-modwrench/thunderstore-get-mod.md
- `thunderstore_list_communities` — Read — https://policylayer.com/tools/171county-modwrench/thunderstore-list-communities.md
- `thunderstore_list_mods` — Read — https://policylayer.com/tools/171county-modwrench/thunderstore-list-mods.md
- `thunderstore_mod_versions` — Read — https://policylayer.com/tools/171county-modwrench/thunderstore-mod-versions.md
- `thunderstore_search_mods` — Read — https://policylayer.com/tools/171county-modwrench/thunderstore-search-mods.md
- `thunderstore_top_mods` — Read — https://policylayer.com/tools/171county-modwrench/thunderstore-top-mods.md
- `mw_activate_platform` — Write — https://policylayer.com/tools/171county-modwrench/mw-activate-platform.md
- `mw_deck` — Write — https://policylayer.com/tools/171county-modwrench/mw-deck.md
- `thunderstore_resolve_dependencies` — Write — https://policylayer.com/tools/171county-modwrench/thunderstore-resolve-dependencies.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=171county-modwrench · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/171county-modwrench