This is great, question though, since you support coding agents like Claude Code and Codex, they run MCP servers, plugins, web search/fetch and their own telemetry from the dev's machine. Do you give customers guidance or controls for that side, or is it out of scope for the gateway?

▲

liquado 3 hours ago | parent | next [-]

We had a lot of problems letting finding a balance giving technical coworkers acces to live data and AI tools. And there are multiple companies in this space that solve things in multiple ways, we happen to use https://gluondb.com which is what you describe plus BI.

	▲	skinfaxi 2 hours ago \| parent [-]
		Seems like a pretty crowded space.

▲

ericmags 5 hours ago | parent | prev [-]

We do give our customers guidance to make sure they are thinking about this properly. This typically happens during on-boarding.

We also built out pre-defined controls for common tools so they can click a button and not think about it.

▲

projectescape 4 hours ago | parent [-]

Food for thought, tool and MCP calls run locally, but every request carries the tool list and every response carries the model's tool calls, both of which pass through you. You could strip non-approved tools from the request and block calls to them in the response, based on an org allowlist. That gives you org-approved MCP/tool calls without touching the dev's machine.

	▲	ericmags 4 hours ago \| parent [-]
		Great call. We already block certain tool schemas and flag URLs in tool-call arguments, and since we enforce org allowlists for models on every request, extending that to tools/MCP is a natural next step.