You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The `origin` field was part of the `set_config_value` tool's input schema,
meaning any AI agent could pass `origin: "ui"` to bypass the security-critical
key lockdown. This completely undermined the protection added in the previous
commit.
Changes:
- Remove `origin` from SetConfigValueArgsSchema (no longer caller-supplied)
- Add trusted `callerOrigin` parameter to setConfigValue(), set server-side only
- Config editor UI now calls `_internal_set_config_value` (not listed in tool
catalog, so agents cannot discover it) which passes callerOrigin='ui'
- MCP tool `set_config_value` always passes callerOrigin='mcp', unconditionally
blocking security-critical keys regardless of what the agent sends
- Fix contradictory kill_process error that said "use force_terminate for
Desktop Commander sessions" (both tools serve the same purpose)
- Update telemetry to derive call_origin from the handler name, not from
user-supplied arguments
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
0 commit comments