Prerequisites

• I've searched the current open issues
• I've updated to the latest version of Toolbox

Toolbox version

?

Environment

unsure

Client

unsure

Expected Behavior

Standardize Error Propagation: Update the Toolbox to catch GCP HTTP errors (401, 403, 429) and map them to the MCP isError: true result object with original codes.

MCP Specification: Concepts: Tools - Error Handling

Current Behavior

When Dataplex Search API returns 403 Forbidden (permission denied), MCP Toolbox fails to surface the code. It instead reports generic "connection interrupted" errors.

Impact: Turned a 5-minute permission fix into an intensive manual log-mining exercise. This "silent failure" erodes developer trust in the Toolbox as it obscures critical GCP security telemetry.

Steps to reproduce?

• Call Dataplex Search via MCP with insufficient IAM roles.
• Observe generic error in logs.
• Manually mine Dataplex API-specific logs to find the hidden 403 error.

Additional Details

No response