MCP server limitations

Known limitations for MCP server integration in the Aisera Platform.

The following limitations apply to MCP server integration in the Aisera Platform.

Tenant and tool limits

• Tenants can register a maximum of 10 tools at one time.

Access control

• Tool-level, user-specific access control is not available. All registered tools are available to all AiseraGPT channel users.

• The Aisera Platform provides no mechanism to carry an individual end-user's identity or access token to the upstream MCP server. All tool calls use a shared service-account credential at the tenant level.

Workflow integration

• Flows and HyperFlows cannot call MCP tools.

Execution

• Mid-process elicitation is not supported.

• Long-running processes are not supported.

Input handling

• The WebEx input form does not consistently render for MCP tools with more than six parameters.

• The input form does not identify required fields.

• Slot filling may populate incorrect field values in some cases.

• Part of a user query is sometimes treated as a parameter value without prompting the user for input.

UI and reporting

• The request page does not show the fulfillment source and type.

• Language translation for tool disambiguation is inconsistent.

• No thumbs up/down feedback is available after a successful external tool call.

• The summarized answer may show an external tool status error code.

Server sync

• If the MCP server provider updates or deletes a tool that is currently registered to an application, runtime execution of that tool may be affected. Update the tool manually in the Aisera Platform admin console.