Boomi's July release: Agent Control Tower watches agents on other platforms

Two months after Boomi World, Boomi’s July release fills in the details. Most of it is about agents, and one feature stands out for integration teams: Agent Control Tower now watches agents that do not run in Boomi at all.

What Boomi released

The main features, all generally available unless noted:

• Agent Control Tower has extended its monitoring. It now shows how agents use Knowledge Hub and Meta Hub, and its anomaly detection covers agents in Amazon Bedrock and agents from custom providers, not only Boomi’s own.
• Agentstudio APIs are now public, so agents can be created and managed from code and pipelines, not only from the interface.
• Agent improvements include linking Meta Hub glossaries to agent tasks, streaming of the agent’s reasoning in real time, memory across conversations and file input.
• Boomi Companion, the open-source set of agent skills that lets people work with Boomi in natural language from Claude, Gemini or Copilot, is generally available.
• Knowledge Hub is in early access. It is a managed RAG service that handles ingestion, chunking, embedding, vector storage and retrieval, and connects directly to Agentstudio.
• API management gets controls for which MCP servers are visible, custom host names for the developer portal, HMAC authentication and editing of GraphQL documentation.
• Boomi for SAP 2.1 has received SAP’s Clean Core certification.

Why it matters

Monitoring agents on other platforms is the most important change. Most large companies will have agents in several places: in the cloud providers’ platforms, in business applications and in the integration platform. A control tower that only sees its own agents does not answer the question management asks, which is what all the agents are doing.

The MCP visibility controls in API management point the same way. When APIs and integrations are exposed as MCP servers, someone has to decide which agents and teams should see which servers. Putting that in the API management layer, where access to APIs is already controlled, is a natural choice.

How it compares

Boomi is not alone in wanting to see agents across platforms. ServiceNow, MuleSoft and the cloud providers all offer some version of this. The difference lies in how deep the view goes: whether the tool only lists agents, or can also see what they do and raise an alarm when something unusual happens.

What to ask

1. Which agents are visible? Check which of your platforms Agent Control Tower can actually monitor, and which agents are still outside it.
2. What counts as an anomaly? Ask what the anomaly detection looks for, and who is alerted.
3. Who decides MCP visibility? Agree who approves which MCP servers are visible to which teams and agents.