Repository navigation
Conversation
Add a per-server tool_argument_error_mode policy (detailed|redacted) persisted through config, storage, REST and MCP management, and consulted at dispatch by the call_tool_* variants, the legacy call_tool handler and direct routing mode. Redacted renders eligible argument errors as the existing self-healing invalid_params envelope with the message "Invalid tool arguments." while every other failure and the default/detailed policies stay byte-identical. Add regression coverage and regenerate the tools/list goldens and OpenAPI artifacts.
|
Codecov Report❌ Patch coverage is 📢 Thoughts on this report? Let us know! |
|
Merged — thank you @antongulin! The opt-in One note from review, not a blocker: activity records still keep the unredacted error (as your docs say, logs are out of scope). If you're interested, extending the policy to the activity If you feel like sharing what you built (a post, a tweet, anywhere), we'd love to boost it — no pressure at all. |
Some error messages repeat private information. This adds an optional privacy setting to hide those details while still helping the AI fix its request.
Description
Adds optional per-upstream
tool_argument_error_mode: "redacted"to hide recognized argument-error details while keeping the schema and retry hint. Default behavior stays unchanged. Configurable through REST/MCP; coverscall_tool_*, legacycall_tool, and direct routing.Generic SDK
Invalid paramserrors, upstreamisErrorresults, logs, and sandbox errors remain outside this policy. No dependency or UI/CLI changes.Testing
CI: 42 passed, 8 skipped. Focused race tests, builds, and API E2E (70/70) pass. The unrestricted local server suite had remaining failures.