thunderstore_resolve_dependencies

SERVERModWrench MCP Server SOURCE@modwrench/cli

Medium RISK CLASS

Category Write

Parameters 32 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/171county-modwrench/thunderstore-resolve-dependencies.md

WHAT IT DOES

What thunderstore_resolve_dependencies does on ModWrench MCP Server

AI agents use thunderstore_resolve_dependencies to create or update resources in ModWrench MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ModWrench MCP Server environment.

Parameter	Type	Required	Description
`name`	string	Yes	Mod name — the part after the dash in full_name.
`maxDepth`	integer	—	How deep to walk the tree. Default 6 — deep enough for real BepInEx stacks, capped so a pathological graph can't run away.
`namespace`	string	Yes	Mod author/namespace — the part before the dash in full_name.

Parameters from the server's own tool schema.

RISK

Why thunderstore_resolve_dependencies is rated Medium

An AI agent can call thunderstore_resolve_dependencies faster than any human can review: one bad instruction and it creates or modifies resources in ModWrench MCP Server by the hundred, each call as confident as the last.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

thunderstore_resolve_dependencies Rate-limited

thunderstore_resolve_dependencies stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "thunderstore_resolve_dependencies": {
      "limits": [
        {
          "counter": "thunderstore_resolve_dependencies_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

FAQ

Questions about thunderstore_resolve_dependencies

What does the thunderstore_resolve_dependencies tool do? +

Resolve a Thunderstore mod's ENTIRE dependency tree — not just its direct deps, but its deps' deps, all the way down. De-duped and cycle-safe; returns an install-first order (dependencies before the things that need them), the full tree, and any refs it couldn't resolve. The 'find every mod this needs before I download it' answer in one shot. Read-only. It is categorised as a Write tool in the ModWrench MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does thunderstore_resolve_dependencies accept? +

thunderstore_resolve_dependencies accepts 3 parameters: name, maxDepth, namespace. Required: name, namespace. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on thunderstore_resolve_dependencies? +

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

thunderstore_resolve_dependencies is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit thunderstore_resolve_dependencies? +

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

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

thunderstore_resolve_dependencies 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

resolve_projects on ACE-MCP →resolve_circuit on 0gzk → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →