[Bug]:Unable to see request payload being sent

[vksinha10]

While working with mcp-context-forge, I am unable to view the request payload that is being sent. This makes it difficult to debug and validate what data is actually leaving the client.

Steps to Reproduce:

Send a request using the MCP client.

Check the logs / debug output.

Observe that the request payload is not visible.

Expected Behavior:
The request payload should be logged or accessible (at least in debug mode) so developers can confirm what data is being transmitted.

Actual Behavior:
Only metadata and response information are visible. The request payload itself is missing from logs/outputs.

[vksinha10]

When working with mcp-gateway, I am unable to view the request payload being sent. This makes it very difficult to debug and validate tool registration requests. Even though sensitive fields can be masked, the raw payload (or at least a redacted version) should be visible.

Steps to Reproduce:

Enable file logging with the following configuration:

LOG_TO_FILE=true
LOG_FILEMODE=a+
LOG_FILE=mcpgateway.log
LOG_FOLDER=logs
LOG_LEVEL=INFO

Start the gateway.

Register a tool in MCP Gateway.

Try to test the tool.

Inspect the logs/mcpgateway.log file.

Expected Behavior:

The request payload (with sensitive fields masked if necessary) should be visible in mcpgateway.log.

Debug-level logs should show what is being sent from the client to the gateway.

Actual Behavior:

No request payload is logged in mcpgateway.log.

The only output is the error response from the gateway:

{
"jsonrpc": "2.0",
"error": {
"code": -32000,
"message": "Invalid method",
"data": {
"grant_type": "",
"username": "",
"password": "******"
}
},
"id": 1758624387514
}

Impact:
Without access to request payload logging, it’s hard to know if the error is due to:

Payload formatting issue

Wrong JSON-RPC method name

Gateway stripping/masking fields incorrectly