The safeguards map / 3.3 Gateways

Lunar MCPX

Lunar.dev (company). No foundation, released. MIT. Listed; as of .

Drafted with AI

Drafted with AI from the cited sources under the direction of UnGovr staff. UnGovr holds editorial responsibility for this page. How this site is made

An open-source aggregator that puts several Model Context Protocol (MCP) servers behind one gateway endpoint, from a project that also describes tool-access control for agent traffic.

Where it sits

3.3 Gateways (primary): Aggregates several MCP servers behind one gateway endpoint; the parent project describes controlling tool access with fine-grained rules.

Control tool access, throttle agent actions, and govern agentic traffic with fine-grained rules.

captured

Lunar MCPX is an MCP server which serves as an aggregator for other MCP servers.

captured

consolidating multiple MCP servers into a single gateway, enhancing security, observability, and management

captured

Facts

Concern
security
Names the law
no
Subject
agentAI system
Used by
those who run it
Runs
at runtime
Policy comes from
owner-entered settings
Traffic it sees
tool calls (MCP)
Can the agent bypass it
depends

Handoffs

None recorded.

Listed, not drawn: no documented handoff and no foundation home places it on the map.

Collector's note

Thin evidence: the MCPX README documents aggregation only, and the policy sentence comes from the parent project README, which covers the Lunar Proxy too. The README also says the project is free for non-production and personal use while the license file is MIT. docs.lunar.dev now serves Boomi documentation, which is not cited because it describes another edition.

Every quote is verbatim from a stored capture of the page linked under it. Placement is our reading of the product's own documentation; no publisher has reviewed or endorsed it. Rows CC BY 4.0. Names, marks and logos belong to their owners; logos identify each product and are not part of the dataset.