NousResearch/hermes-agent

Enforce allowed_tools allowlist for MCP servers

Cluster 106983 · mcp. Data as of

1 open item. Fix attempted, not merged.

The short answer

1open issue
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 0 PRs.

These issues and PRs concern a configuration field mcp_servers.<name>.allowed_tools that is declared but not enforced as a tool allowlist. The work involves implementing enforcement of this whitelist for MCP server tool access.

Open issues1

  • Issue#106983mcp_servers.<name>.allowed_tools is declared but never enforced

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: done elsewhere 1 · other 1

  • #106989 fix(security): enforce mcp_servers.<name>.allowed_tools whitelist · done elsewhere → #106983, #126199
  • #126199 fix(mcp): enforce mcp_servers.<name>.allowed_tools as tool allowlist · other → 6d32d8d
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
mcp
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.