UCL

Tools and databases

How the gateway names tools and turns a database into governed MCP tools.

Tool namespacing

Every tool is namespaced so calls route to the right source: <connector>__<tool> for an MCP server (e.g. slack__send_message) and <source>__<tool> for a database source.

Databases as tools

Connect a SQL-over-HTTP source and the gateway generates curated, bounded tools (list/read/create/update) per table - governed by the same RBAC, column rules, and audit as any MCP tool. The gateway never holds a service-role key.

Per-tool config

  • description: override the prompt agents see for a tool.
  • blockInput: input fields hidden from the schema and stripped from calls.
  • redactOutput: result fields removed from responses.
  • fieldDescriptions: per-field description overrides shown to agents.

Last updated 2026-06-09