Label packs
Label packs map popular MCP servers’ tools to sources and sinks, so a policy doesn’t start from
nothing. They’re built into garm; garm init adds the ones it recognises, and
garm policy packs lists them.
packs:
- github # for `garm mcp-proxy --name github`
- { pack: filesystem, server: fs } # for `garm mcp-proxy --name fs`
| Pack | Server | Reads | Sends |
|---|---|---|---|
github | github/github-mcp-server | untrusted | reads stay inside; writes public |
filesystem | @modelcontextprotocol/server-filesystem | trusted (DLP raises it) | stays local |
fetch | mcp-server-fetch | untrusted | public |
git | mcp-server-git | trusted; history from colleagues | stays local |
slack | @modelcontextprotocol/server-slack | internal, from colleagues; profiles PII | posts up to confidential |
postgres | @modelcontextprotocol/server-postgres | confidential, PII | stays inside |
brave-search | Brave Search | untrusted | public |
playwright | microsoft/playwright-mcp | untrusted | public |
notion | Notion (hosted and open source) | internal, from colleagues | writes up to internal |
sentry | getsentry/sentry-mcp | confidential, PII, untrusted | writes up to internal |
Packs are a starting point
- Your entries can only make a pack stricter. Matching sources combine and the strictest
matching sink wins, so a
sourcesentry can raise a pack’s label (your repos are private) but asinksentry can’t loosen one. To loosen, copy the pack’s entries into your policy instead. - Tools a pack doesn’t name stay unmapped: untrusted and internal when read, public and external when called. Servers add tools between releases, and new ones fail closed.
- Some packs favour everyday use. GitHub content and Playwright pages are labelled public rather than internal, so reading an issue and then fetching docs isn’t held. Raise them in your policy if your repos or browser sessions are private.