fix(mcp): make tool approval annotations explicit

[cameroncooke]

Summary

• make MCP approval annotations explicit across all static tool manifests
• ensure proxied Xcode IDE bridge tools always register a complete approval annotation set
• add tests that fail if manifests or discovered tools omit the required approval hints

Context

Codex now treats missing MCP approval hints as risky defaults. This change makes the approval-related annotations explicit so local XcodeBuildMCP tools can stay low-friction while still describing their behavior honestly.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/xcodebuildmcp@297

commit: 093b91f

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

[cursor]

Simulator-mutating tools incorrectly marked as read-only

High Severity

set_sim_location, set_sim_appearance, reset_sim_location, and sim_statusbar are all newly marked readOnlyHint: true, yet their implementations execute state-mutating xcrun simctl commands (location set, ui appearance, location clear, status_bar override). The MCP spec defines readOnlyHint: true as "the tool does not modify its environment," and clients skip user-approval dialogs for such tools. This contradicts the PR's stated goal of "describing behavior honestly" and is inconsistent with erase_sims, which is correctly marked readOnlyHint: false.

Additional Locations (2)

• manifests/tools/set_sim_appearance.yaml#L8-L9
• manifests/tools/reset_sim_location.yaml#L8-L9