Integration


This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas

  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Add a new idea Subscribe
Status Submitted
Workspace App Connect
Created by Guest
Created on Aug 12, 2026

RELATED IDEAS

ACE MCP Server to forward protocol information towards downstream REST API flows

It would be useful to see mcp protocol informations and additional mcp fields in the downstream rest-api flow, either under LocalEnvironment.MCP or in the HTTPInputHeader.

An actual business requirement, that we have:

we must be able to send data from the MCP Client towards the backend without including it in the service definition yaml (so that the LLM won't be able to change it, e.g. username claim for the backend)

I have tried to add this information into the _meta section of the MCP call, but those fields are somehow swallowed by ACE, when the call reaches the REST API flow.

Neither was the authentication field of the mcp client "proxied" downstream.

Idea priority High
  • Guest
    Aug 13, 2026

    I would like to emphasize that this is a crucial capability for enterprise MCP server implementations, especially for security-sensitive integrations.

    MCP defines _meta as the mechanism for attaching additional request metadata. We need to pass trusted per-request execution context (user identity, auth scope, security metadata) from MCP layer to downstream REST flows without exposing it as tool input, since tool arguments are model-controlled and can be modified by the LLM.

    ACE should therefore preserve MCP _meta and expose it to the downstream flow (e.g. via LocalEnvironment.MCP), along with validated authentication claims.

    The MCP bearer token itself should not be forwarded downstream; instead, ACE should expose the authenticated principal/claims so backend-specific credentials or headers can be derived securely.

    Without this non-LLM-controlled context, secure enterprise MCP integrations are not feasible.

    Reply

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.