thunderstore_list_mods
List mods in a specific Thunderstore community. Returns a summary view per mod (name, author, rating, downloads, latest version). Paginated server-side; default page size is whatever the community returns.
This record as markdown: /tools/171county-modwrench/thunderstore-list-mods.md
What thunderstore_list_mods does on ModWrench MCP Server
AI agents call thunderstore_list_mods 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 |
|---|---|---|---|
limit | integer | — | Max results to return (1-100). Default 30. |
community | string | Yes | Community identifier (e.g. 'lethal-company'). |
Parameters from the server's own tool schema.
Why thunderstore_list_mods is rated Low
This tool queries public mod listing data from Thunderstore and presents it to the user. It retrieves information without creating, modifying, deleting, or executing any operations. Even if an AI agent misuses it, it cannot cause harm—at worst, it may make unnecessary API calls. The blast radius is minimal, making this a low-severity Read operation.
From the tool's definition Tool 'thunderstore_list_mods' retrieves and returns mod summaries (name, author, rating, downloads, latest version) from Thunderstore with no modification capability.
Attacks that exploit this kind of access
The rule that runs thunderstore_list_mods 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_list_mods, this is the rule to start with:
thunderstore_list_mods 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_list_mods call is checked against it from then on.
Questions about thunderstore_list_mods
List mods in a specific Thunderstore community. Returns a summary view per mod (name, author, rating, downloads, latest version). Paginated server-side; default page size is whatever the community returns. It is categorised as a Read tool in the ModWrench MCP Server MCP Server, which means it retrieves data without modifying state.
thunderstore_list_mods accepts 2 parameters: limit, community. Required: community. 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_list_mods: 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_list_mods 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_list_mods 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_list_mods. 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_list_mods 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