thunderstore_mod_versions
List the full version history of a specific mod. Each entry includes version number, download count, file size, dependencies, and release date. Newest first. Version history is only available via the community listing endpoint, so a community must be specified — pick any community the mod is publ...
This record as markdown: /tools/171county-modwrench/thunderstore-mod-versions.md
What thunderstore_mod_versions does on ModWrench MCP Server
AI agents call thunderstore_mod_versions 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Mod name. |
community | string | Yes | Community identifier (e.g. 'lethal-company'). Any community where the mod is listed; the version history is identical across communities. |
namespace | string | Yes | Mod author/namespace. |
Parameters from the server's own tool schema.
Why thunderstore_mod_versions is rated Low
Even though thunderstore_mod_versions 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
The rule that runs thunderstore_mod_versions 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_versions, this is the rule to start with:
thunderstore_mod_versions is read-only, so it stays allowed. 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_versions call is checked against it from then on.
Questions about thunderstore_mod_versions
List the full version history of a specific mod. Each entry includes version number, download count, file size, dependencies, and release date. Newest first. Version history is only available via the community listing endpoint, so a community must be specified — pick any community the mod is published in (use thunderstore_get_mod's community_listings field to discover). It is categorised as a Read tool in the ModWrench MCP Server MCP Server, which means it retrieves data without modifying state.
thunderstore_mod_versions accepts 3 parameters: name, community, namespace. Required: name, community, 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_versions: 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_versions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the thunderstore_mod_versions 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_versions. 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_versions 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.
This server
Across the catalogue