Access to request authorization header when using MCP tool trigger

[cturner-pulsion]

Is there any way to access the incoming HTTP request headers when using an MCP tool to allow using the access token to invoke an authenticated remote API?

The MCP tool invocation context does not appear to have access to this information already and there does not seem to be anything present when registering a custom hook either.