mw_parse_crashlog

SERVERModWrench MCP Server SOURCE@modwrench/cli

High RISK CLASS

Category Execute

Parameters 30 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/171county-modwrench/mw-parse-crashlog.md

WHAT IT DOES

What mw_parse_crashlog does on ModWrench MCP Server

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.

Parameter	Type	Required	Description
`logPath`	string	—	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	—	Format hint. Default 'auto' — detect from content. Pass an explicit type when the auto-detect heuristic fails on a truncated log.
`logContent`	string	—	Crashlog file content as a string. Provide this OR logPath.

Parameters from the server's own tool schema.

RISK

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mw_parse_crashlog safely

PolicyLayer is an MCP gateway: it sits between your AI agents and ModWrench MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mw_parse_crashlog, this is the rule to start with:

mw_parse_crashlog Rate-limited

mw_parse_crashlog stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mw_parse_crashlog": {
      "limits": [
        {
          "counter": "mw_parse_crashlog_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ModWrench MCP Server, apply this rule, and every mw_parse_crashlog call is checked against it from then on.

FAQ

Questions about mw_parse_crashlog

What does the mw_parse_crashlog tool do? +

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". It is categorised as a Execute tool in the ModWrench MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does mw_parse_crashlog accept? +

mw_parse_crashlog accepts 3 parameters: logPath, logType, logContent. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on mw_parse_crashlog? +

Register the ModWrench MCP Server MCP server in PolicyLayer and add a rule for mw_parse_crashlog: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches ModWrench MCP Server. Nothing to install.

What risk level is mw_parse_crashlog? +

mw_parse_crashlog is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit mw_parse_crashlog? +

Yes. Add a rate_limit block to the mw_parse_crashlog rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block mw_parse_crashlog completely? +

Set action: deny in the PolicyLayer policy for mw_parse_crashlog. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides mw_parse_crashlog? +

mw_parse_crashlog is provided by the ModWrench MCP Server MCP server (@modwrench/cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ModWrench MCP Server, and thousands of servers like it.

This server

All 17 ModWrench MCP Server tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →