thunderstore_search_mods
Search mods in a Thunderstore community by name substring. Case-insensitive. Returns a summary view per match.
This record as markdown: /tools/171county-modwrench/thunderstore-search-mods.md
What thunderstore_search_mods does on ModWrench MCP Server
AI agents call thunderstore_search_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 (1-50). Default 20. |
query | string | Yes | Substring to match against mod name (case-insensitive). |
community | string | Yes | Community identifier. |
Parameters from the server's own tool schema.
Why thunderstore_search_mods is rated Low
This tool retrieves and queries mod metadata from Thunderstore without any side effects. It is a search operation that returns read-only summary data. No data is created, modified, deleted, or executed. The case-insensitive substring matching is a standard search feature with no destructive or operational impact.
From the tool's definition Tool performs search functionality ('Search mods in a Thunderstore community by name substring') and 'Returns a summary view per match' - purely informational retrieval with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs thunderstore_search_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_search_mods, this is the rule to start with:
thunderstore_search_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_search_mods call is checked against it from then on.
Questions about thunderstore_search_mods
Search mods in a Thunderstore community by name substring. Case-insensitive. Returns a summary view per match. It is categorised as a Read tool in the ModWrench MCP Server MCP Server, which means it retrieves data without modifying state.
thunderstore_search_mods accepts 3 parameters: limit, query, community. Required: query, 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_search_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_search_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_search_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_search_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_search_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