# thunderstore_get_community

Get details for a single Thunderstore community (game) by its identifier. Returns name, links (Discord, wiki), and metadata flags. Thunderstore has no single-community detail endpoint — this walks the paginated list and early-exits on match, so cost grows with how late in the list the target is.

Agent View of the PolicyLayer registry record for `thunderstore_get_community`. HTML page: https://policylayer.com/tools/171county-modwrench/thunderstore-get-community

## Facts

- Tool: `thunderstore_get_community`
- Server: ModWrench MCP Server (`@modwrench/cli`) — https://policylayer.com/tools/171county-modwrench.md
- Install: `npx -y @modwrench/cli`
- Homepage: https://github.com/171county/modwrench
- Risk category: Read (Low risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `identifier` | string | yes | Community identifier (slug) — e.g. 'lethal-company', 'valheim', 'risk-of-rain-2'. Use thunderstore_list_communities to discover these. |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "thunderstore_get_community",
    "arguments": {
      "identifier": "<identifier>"
    }
  }
}
```

## Why thunderstore_get_community is rated Low

This tool performs a simple data retrieval operation (searching paginated community list and returning metadata). It has no side effects, cannot modify state, and presents minimal risk even if misused by an AI agent. The only minor consideration is inefficient pagination usage if called repeatedly, but this is a performance issue rather than a security risk. Classified as Read with low severity and high confidence.

From the tool's own definition: "Tool retrieves details for a Thunderstore community by identifier, returning name, links, and metadata flags. No modification, deletion, or execution capabilities—purely informational lookup."

## Use case

AI agents call thunderstore_get_community 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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches ModWrench MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "thunderstore_get_community": {}
  }
}
```

## Other tools on ModWrench MCP Server (16)

- `mw_parse_crashlog` — Execute — https://policylayer.com/tools/171county-modwrench/mw-parse-crashlog.md
- `thunderstore_mod_dependencies` — Execute — https://policylayer.com/tools/171county-modwrench/thunderstore-mod-dependencies.md
- `mw_check_known_conflicts` — Read — https://policylayer.com/tools/171county-modwrench/mw-check-known-conflicts.md
- `mw_detect_environment` — Read — https://policylayer.com/tools/171county-modwrench/mw-detect-environment.md
- `mw_diagnose_crash` — Read — https://policylayer.com/tools/171county-modwrench/mw-diagnose-crash.md
- `mw_query_mod_metadata` — Read — https://policylayer.com/tools/171county-modwrench/mw-query-mod-metadata.md
- `mw_read_load_order` — Read — https://policylayer.com/tools/171county-modwrench/mw-read-load-order.md
- `thunderstore_get_mod` — Read — https://policylayer.com/tools/171county-modwrench/thunderstore-get-mod.md
- `thunderstore_list_communities` — Read — https://policylayer.com/tools/171county-modwrench/thunderstore-list-communities.md
- `thunderstore_list_mods` — Read — https://policylayer.com/tools/171county-modwrench/thunderstore-list-mods.md
- `thunderstore_mod_versions` — Read — https://policylayer.com/tools/171county-modwrench/thunderstore-mod-versions.md
- `thunderstore_search_mods` — Read — https://policylayer.com/tools/171county-modwrench/thunderstore-search-mods.md
- `thunderstore_top_mods` — Read — https://policylayer.com/tools/171county-modwrench/thunderstore-top-mods.md
- `mw_activate_platform` — Write — https://policylayer.com/tools/171county-modwrench/mw-activate-platform.md
- `mw_deck` — Write — https://policylayer.com/tools/171county-modwrench/mw-deck.md
- `thunderstore_resolve_dependencies` — Write — https://policylayer.com/tools/171county-modwrench/thunderstore-resolve-dependencies.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=171county-modwrench · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/171county-modwrench