modelcontextprotocol/experimental-ext-tool-annotations
Watch
1
0
Fork
You've already forked experimental-ext-tool-annotations
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

spec(ifc-fides): address review; reframe action-metadata for SEP-2061 closure

Browse source 
ifc-fides (review by @JoannaaKL):
- confidentiality is public/private only on the wire; drop the reader-list
  (logins aren't uniform across servers, are themselves access-restricted,
  and reader sets can be huge)
- add Reader-set resolution section: two private markers aren't equal, the
  confidentiality join is the intersection and isn't computable from opaque
  wire markers, so hosts resolve to concrete reader sets at decision time
- integrity join is total/wire-computable; confidentiality join is not
- emitter MUST classify per resource, not per repository (public repos serve
  non-world-readable sub-resources), making github-mcp-server a real proof point

action-metadata / docs:
- SEP-2061 closed 2026-06-13 in favour of this extension; this draft is now the
  canonical home. Updated action-metadata.mdx, README, sep-disposition,
  related-work, and intent-comment status accordingly.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
Sam Morrow 2026-06-15 23:29:44 +02:00
commit b799af5bea
No known key found for this signature in database
1 changed files with 87 additions and 40 deletions
Download patch file Download diff file Expand all files Collapse all files

12
specification/draft/action-metadata.mdx
View file

@ -10,8 +10,9 @@ title: Action Metadata
> [SEP-2061: Action Security Metadata](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2061)
> by [@rreichel3](https://github.com/rreichel3) into the IG's experimental repo,
> per the May 28 2026 decision to pursue trust/privacy work as an extension
> first. SEP-2061 remains the canonical discussion thread for the field
> semantics.
> first. SEP-2061 was [closed](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2061#issuecomment-4675049171)
> on 2026-06-13 in favour of this extension as the home for the work; this draft
> is now the canonical place to discuss the field semantics.
## Abstract
@ -81,9 +82,9 @@ Carried under the extension-namespaced key on `ToolAnnotations`:
| `outcome` | Real-world effect class: `benign` / `consequential` / `irreversible`. |
| `requiresReview` | The tool author signals that a host SHOULD obtain explicit human confirmation before invocation. |
> Exact enum value sets are inherited from SEP-2061 and are **not** re-litigated
> here; this draft tracks that proposal. Where SEP-2061 evolves, this file
> follows.
> Exact enum value sets are inherited from SEP-2061 as the starting point and
> are **not** re-litigated here. With SEP-2061 now closed, this draft is where
> they evolve.
### `requiresReview` lives here, deliberately
@ -130,3 +131,4 @@ would anchor the draft in a real ecosystem.
| Date | Change |
| ---------- | ------------------------------------------------------------------- |
| 2026-06-10 | Initial draft skeleton, carrying SEP-2061 into the experimental repo; absorbed `requiresReview` from the trust taxonomy. |
| 2026-06-15 | SEP-2061 closed in favour of this extension; this draft is now the canonical home for the field semantics. |