# mw_parse_crashlog

Crash log in, structure out. Parses a crashlog (file path or pasted content) into fields: exception type, call stack, loaded plugins, registers, suspected FormID refs. Handles Crash Logger SSE (Skyrim), Buffout 4 (Fallout 4), NetScriptFramework (older Skyrim), and BepInEx (Unity). Returns parsed structure only — naming the culprit is the model's job, reasoned over the actual load order, not pattern-matched from a list. Use when the user says "my game crashed", "CTD", "here's my crash log", or "why did it crash".

Agent View of the PolicyLayer registry record for `mw_parse_crashlog`. HTML page: https://policylayer.com/tools/171county-modwrench/mw-parse-crashlog

## Facts

- Tool: `mw_parse_crashlog`
- 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: Execute (High risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 3
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `logPath` | string | no | Absolute path to a crashlog file on disk. Common locations: ~/Documents/My Games/Skyrim Special Edition/SKSE/crash-*.log for Crash Logger SSE, ~/Documents/My Ga |
| `logType` | string | no | Format hint. Default 'auto' — detect from content. Pass an explicit type when the auto-detect heuristic fails on a truncated log. |
| `logContent` | string | no | Crashlog file content as a string. Provide this OR logPath. |

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_parse_crashlog",
    "arguments": {}
  }
}
```

## Why mw_parse_crashlog is rated High

mw_parse_crashlog triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

## Use case

AI agents invoke mw_parse_crashlog to trigger actions in ModWrench MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. 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_parse_crashlog": {
      "limits": [
        {
          "counter": "mw_parse_crashlog_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on ModWrench MCP Server (16)

- `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
- `mw_read_load_order` — Read — https://policylayer.com/tools/171county-modwrench/mw-read-load-order.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