MCP adversarial probe rejects the new calternal_calendar tool #564

Open
opened 2026-10-01 02:42:00 +00:00 by kayg · 1 comment
Owner

Found during the focused API/MCP adversarial round on job/floating-sheet at e531cbf03a5606ff5b9658d6813eb67600ac37c7 after merging origin/dev.

tests/adversarial/mcp_probe.py requires an exact set of 11 tools. MCP Inspector returned 12, with the additional calternal_calendar tool, and the probe stopped at the exact-set assertion before exercising its MCP calls. The sidecar live-server probe passed. This appears to be probe/API contract drift; the probe did not establish whether the new tool should be registered or added to the expected contract.

I did not change the existing expectation, per the owner rule. Please decide whether to add and exercise calternal_calendar in the probe or update the server registration.

Found during the focused API/MCP adversarial round on `job/floating-sheet` at `e531cbf03a5606ff5b9658d6813eb67600ac37c7` after merging `origin/dev`. `tests/adversarial/mcp_probe.py` requires an exact set of 11 tools. MCP Inspector returned 12, with the additional `calternal_calendar` tool, and the probe stopped at the exact-set assertion before exercising its MCP calls. The sidecar live-server probe passed. This appears to be probe/API contract drift; the probe did not establish whether the new tool should be registered or added to the expected contract. I did not change the existing expectation, per the owner rule. Please decide whether to add and exercise `calternal_calendar` in the probe or update the server registration.
Author
Owner

A follow-up run of ADVERSARIAL_API_ONLY=1 on job/tasks-mode at f620390c724ee08540d38b0ba69c3d12225fc1e4 did not reach the MCP tool-set check. tests/adversarial/mcp_probe.py failed during setup because its mcp-passwords.json fixture was absent from the new ADVERSARIAL_WORK_DIR:

FileNotFoundError: [Errno 2] No such file or directory: '<work-dir>/mcp-passwords.json'

The runner continued through the sidecar and API probes, but recorded a failed MCP probe. This is separate from the exact-tool-set mismatch already described here; setup must provision the fixture before MCP behavior can be checked.

A follow-up run of `ADVERSARIAL_API_ONLY=1` on `job/tasks-mode` at `f620390c724ee08540d38b0ba69c3d12225fc1e4` did not reach the MCP tool-set check. `tests/adversarial/mcp_probe.py` failed during setup because its `mcp-passwords.json` fixture was absent from the new `ADVERSARIAL_WORK_DIR`: ```text FileNotFoundError: [Errno 2] No such file or directory: '<work-dir>/mcp-passwords.json' ``` The runner continued through the sidecar and API probes, but recorded a failed MCP probe. This is separate from the exact-tool-set mismatch already described here; setup must provision the fixture before MCP behavior can be checked.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
kayg/calternal#564
No description provided.