thunderstore_mod_dependencies
List the dependencies of a Thunderstore mod's latest version — the other packages (e.g. BepInEx) it needs to run. The backbone of a correct r2modman profile. Returns each dependency's full_name.
This record as markdown: /tools/171county-modwrench/thunderstore-mod-dependencies.md
What thunderstore_mod_dependencies does on ModWrench MCP Server
AI agents invoke thunderstore_mod_dependencies 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 |
|---|---|---|---|
name | string | Yes | Mod name — the part after the dash in full_name. |
namespace | string | Yes | Mod author/namespace — the part before the dash in full_name. |
Parameters from the server's own tool schema.
Why thunderstore_mod_dependencies is rated High
thunderstore_mod_dependencies 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
The rule that runs thunderstore_mod_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_mod_dependencies, this is the rule to start with:
thunderstore_mod_dependencies 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.
The button opens the PolicyLayer dashboard: create your workspace, connect ModWrench MCP Server, apply this rule, and every thunderstore_mod_dependencies call is checked against it from then on.
Questions about thunderstore_mod_dependencies
List the dependencies of a Thunderstore mod's latest version — the other packages (e.g. BepInEx) it needs to run. The backbone of a correct r2modman profile. Returns each dependency's full_name. 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.
thunderstore_mod_dependencies accepts 2 parameters: name, namespace. Required: name, namespace. The full parameter table on this page comes from the server's own tool schema.
Register the ModWrench MCP Server MCP server in PolicyLayer and add a rule for thunderstore_mod_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.
thunderstore_mod_dependencies is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the thunderstore_mod_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.
Set action: deny in the PolicyLayer policy for thunderstore_mod_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.
thunderstore_mod_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.
More on ModWrench MCP Server, and thousands of servers like it.
Across the catalogue