Skip to main content
Omni gives each token only the tools that are enabled in AI Hub > MCP and that the user’s roles allow. For example, a Viewer token doesn’t get getData. To narrow what your agent can do for a user, combine the following.

Data access

  • Use the connectionRoles, modelRoles, and userAttributes parameters in your mint calls to control which connections, models, and rows the user can query.
  • Define access filters in your model to set up row-level filters using userAttributes. An attribute doesn’t filter anything until a topic’s access filter uses it. Take attribute values such as tenant_id from the user’s authenticated session on your server, never from a request the client controls.

Topics

  • Use the ai_chat_topics model parameter to limit which topics the AI can pick.
  • Use the X-MCP-Model-ID and X-MCP-Topic-Name headers to pin a session to one model or topic.

MCP tools

Your agent is the MCP client, so it decides which tools the LLM sees. After calling tools/list, pass only the tools you want, such as pickModel, pickTopic, and getData, to your LLM. Hosted agent APIs that take an MCP endpoint URL usually accept an allowed-tools list that does the same thing.
Omni doesn’t check which tools your agent passes to the LLM. On the server, Omni limits tools only by the AI Hub > MCP settings and the user’s roles. askOmni calls other tools on the server, and your tool list has no effect on those calls. What askOmni can do is limited only by the user’s own access.

Next steps