Skip to content

tech-debt-backlog §7.17: gloss tools/call as MCP jargon in README #141

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jascal wants to merge 1 commit into from
Closed

tech-debt-backlog §7.17: gloss tools/call as MCP jargon in README #141

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -865,12 +865,12 @@ Add to your Claude Code settings (`~/.claude/settings.json` or project `.claude.

### Trust Boundary

The server speaks JSON-RPC over **stdio only**. There is no auth check on
`tools/call` — any client that can connect to the stdio pipe can invoke any
tool, including the two that spend on an LLM provider (`generate_machine`,
`refine_machine`). This is intentional: under stdio the client is a local
process the user already started, so the OS process boundary is the trust
boundary.
The server speaks JSON-RPC over **stdio only**. There is no auth check on the
JSON-RPC `tools/call` method (the MCP-standard tool-invocation entry point) —
any client that can connect to the stdio pipe can invoke any tool, including
the two that spend on an LLM provider (`generate_machine`, `refine_machine`).
This is intentional: under stdio the client is a local process the user
already started, so the OS process boundary is the trust boundary.

This property is invisible from the outside, so operators (and anyone wiring
the server up to a new transport) should know:
Expand Down
15 changes: 14 additions & 1 deletion openspec/changes/tech-debt-backlog/tasks.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1549,7 +1549,7 @@ picked up.
(Source: 2026-05-28 PR #76 review log,
`logs/pr-review-2026-05-28.log`, "forward-link to §4.3".)

- [ ] 7.17 **Gloss `tools/call` as MCP jargon on first use in
- [x] 7.17 **Gloss `tools/call` as MCP jargon on first use in
the README.** Severity: LOW. Surface: `README.md`, the
`### Trust Boundary` subsection ("There is no auth check on
`tools/call` — any client that can connect…"). A reader new
Expand All @@ -1563,6 +1563,19 @@ picked up.
(Source: 2026-05-28 PR #76 review log,
`logs/pr-review-2026-05-28.log`, "gloss `tools/call` as MCP
jargon".)
Took the prescribed wording verbatim. The `### Trust Boundary`
subsection's opening sentence in `README.md` now reads "There
is no auth check on the JSON-RPC `tools/call` method (the
MCP-standard tool-invocation entry point) — any client that
can connect to the stdio pipe can invoke any tool…", glossing
the JSON-RPC method name and naming MCP as the standard that
defines it. No test pins the README prose (`grep -n
'tools/call\|Trust Boundary' tests/` returns nothing in
`tests/test_mcp_server.py` except the sanitizer-related code
paths it covers), so the print-only change is safe. The
follow-up forward-link from §7.16 stays open: it depends on
an MCP-error-handling section that does not yet exist in
`README.md`, so adding the anchor is wider than §7.17 scope.

- [ ] 7.18 **Tighten the prior-Claude-review check from
substring to author identity in `pr-review-prompt.txt`.**
Expand Down