Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Feature: MCP allowlist.

Open
#836 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
go
Domain
ai, api

Research direction

Start by locating the existing model allowlist implementation and tracing how per-key permissions are applied to requests. Then inspect the MCP server and tool filtering entry points to determine where per-key scope could be enforced; the issue does not name specific files or tests. Done means MCP servers or tools are filtered according to the key’s allowlist, with the intended scope behavior covered by tests.

Written by the indexing model from the issue text.

Description

Is your feature request related to a problem? Please describe.
Kinda. I use centralised gateway for everything. There is general agent, coding agent, "minimal" set for testing interesting projects, and so on. However i have like 15 MCP tools in my current gateway (different project), and i assign them per-key as well since not every client needs every tool and enabling them all significantly bloats context.

Describe the solution you'd like
Basically same as model allowlist - per-key mcp allowlist. Enable MCP servers you need for specific task, list gets filtered, key gets served only limited scope. Maybe even per-tool list? For example you have exa mcp. They have web_fetch_exa and web_search_exa tools. You can gate it behind exa/web_search_exa if you want to scope it or grant exa/* access.

Dominant language
Go
Stars
1.2k
Forks
111
Avg merge
17h 1m
Merged PRs (30d)
95

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ENTERPILOT/GoModel

All issues in ENTERPILOT/GoModel

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.