The EDB Platform component connects a flow to the Hybrid Manager (HM) platform's MCP tool surface. It surfaces HM's platform-level operations to an agent on behalf of the calling user, so the agent can list, inspect, and act on the user's HM resources.
Choosing the right component
Use the EDB Platform component when:
- You want an agent to be able to look up information about the caller's HM environment (projects, clusters, knowledge bases) during a flow run.
- You want platform operations available as MCP tools, scoped to the current HM user's permissions.
Use a different component if:
- You want the agent to execute SQL against a specific Postgres database. Use EDB Airman MCP.
- You want a knowledge base similarity search, not platform navigation. Use EDB Knowledge Base.
Prerequisites
- The identity running the flow must have the HM permissions for whichever platform operations the agent invokes. In the flow builder this is the logged-in user; in a deployed flow it is the caller's identity (user or machine user). Tool calls execute with that identity's permissions.
Inputs
| Field | Type | Required | Default | Notes |
|---|---|---|---|---|
| Tool | Dropdown | Yes | Populated from the HM platform MCP server when you select the refresh button. Select the specific tool to invoke. Additional fields appear depending on the tool's arguments. |
When you select a Tool, the component reads the tool's input schema from the MCP proxy and renders one field per argument under the dropdown. Field types and labels come from the tool definition.
Outputs
| Output | Type | Carries |
|---|---|---|
| Response | DataFrame | The selected tool's result, parsed as a DataFrame. JSON outputs are flattened to columns. Errors are returned as a row with an error column rather than raised. |
When the component is used as a tool provider for an agent (instead of being invoked directly), every tool the proxy exposes is registered with the agent and the Tool dropdown is not consulted.
Notes
- Tools are fetched from a running HM-side MCP proxy. Available tools and their argument schemas can change as HM platform features evolve.
- Each tool call carries the calling user's HM identity and session, so platform-side audit logs attribute the action to the user, not to a shared service account.