NetworkPolicy for Headless Services for MCP Servers
Open
Nobody has claimed this yet.
kubernetes
p0
- Dominant language
- Go
- Stars
- 2.2k
- Forks
- 300
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 184
Description
We want to add a NetworkPolicy that restricts all ingress to the MCP servers to only come from the associated proxy. This removes the opporunity for someone to bypass toolhive to get to the MCP Server
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the Kubernetes configuration or controller code that creates headless services for MCP servers and associates them with proxies. Read how ingress is currently configured, then verify that the resulting NetworkPolicy permits traffic only from the associated proxy and blocks direct access to the MCP server.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- infrastructure, networking, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 43/100