JunghwanNA 34fccb2ee9 Prevent self-inspection from leaking configured secrets ...

MyTool blocks direct access to sensitive nested paths, but its formatter
still printed scalar fields for small config objects. That let
`my(action="check", key="web_config.search")` expose `api_key` in plain
text even though the docs promise sensitive sub-fields are protected.

This keeps the change narrow: sensitive nested config fields are omitted
from MyTool's formatted output, and regression coverage locks the
behavior in.

Constraint: Must preserve existing read-only inspection behavior for non-sensitive fields
Constraint: Keep scope limited to MyTool rather than introducing broader redaction plumbing
Rejected: Rework global context/tool redaction around MyTool | broader than needed for the leak path
Confidence: high
Scope-risk: narrow
Reversibility: clean
Directive: If more nested config rendering is added later, filter sensitive field names at the formatter boundary as well as the path resolver
Tested: PYTHONPATH=$PWD pytest -q tests/agent/tools/test_self_tool.py /Users/jh0927/Workspace/nanobot-validation-artifacts-2026-04-18/test_my_tool_secret_leak_regression.py
Not-tested: Full repository test suite
Related: #3259

2026-04-18 00:59:08 +08:00

..

__init__.py

feat(agent): add SelfTool for runtime self-inspection and configuration

2026-04-16 23:44:26 +08:00

test_self_tool.py

Prevent self-inspection from leaking configured secrets

2026-04-18 00:59:08 +08:00

test_subagent_tools.py

fix(exec): pass allowed_env_keys to exec tool calls in subagents

2026-04-17 16:32:25 +08:00