docs(adr): propose that the MCP surface reads no local files #793
No reviewers
Labels
No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sixfold-space/madtea!793
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "docs/adr-mcp-no-file-reads"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
ADR 0055 records a boundary. Over MCP a text payload is literal: the server never reads a local file or stdin for a payload. A server-side read would publish any file the server can read to the forge, and it would skip the outbound-text guards, which see only the tool argument. File input stays on the CLI, where a human types the path, and in the caller, which can read a file into its own context and pass the content inline. The status is proposed. It cites #792, the bug that surfaced it.