mw_detect_environment

SERVERModWrench MCP Server SOURCE@modwrench/cli

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/171county-modwrench/mw-detect-environment.md

WHAT IT DOES

What mw_detect_environment does on ModWrench MCP Server

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

RISK

Why mw_detect_environment is rated Low

Even though mw_detect_environment 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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mw_detect_environment 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_detect_environment, this is the rule to start with:

mw_detect_environment Allowed

mw_detect_environment is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mw_detect_environment": {}
  }
}

ALLOW ONLY 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_detect_environment call is checked against it from then on.

FAQ

Questions about mw_detect_environment

What does the mw_detect_environment tool do? +

See what you're working with. Auto-detects OS, Steam Deck, installed mod-friendly games (Bethesda / Unity co-op), per-game loaders (SKSE / F4SE / BepInEx), mod managers (MO2 / Vortex / r2modman), and Proton versions on Linux. Read-only — reads known config/save locations and touches nothing else. Use when the user asks "what've I got installed", "find my games", or before any tool that needs to know their setup. It is categorised as a Read tool in the ModWrench MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on mw_detect_environment? +

Register the ModWrench MCP Server MCP server in PolicyLayer and add a rule for mw_detect_environment: 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_detect_environment? +

mw_detect_environment is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit mw_detect_environment? +

Yes. Add a rate_limit block to the mw_detect_environment 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_detect_environment completely? +

Set action: deny in the PolicyLayer policy for mw_detect_environment. 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_detect_environment? +

mw_detect_environment 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 →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →