Skip to content
Open
Changes from all commits
Commits
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
8 changes: 8 additions & 0 deletions docs/security-privacy-considerations.md
Original file line number Diff line number Diff line change
Expand Up @@ -360,6 +360,14 @@ To advance the security and privacy posture of WebMCP, we need community input o

**How:** Ensuring an interoperable basis for prompt injection defense, by requiring any implementer to protect against at least the attacks in that dataset

#### [Untrusted Annotation for Tool Responses](https://github.com/webmachinelearning/webmcp/issues/136)

**What:** Giving agents information about trust boundaries such as highlighting untrustworthy content to the model using an untrusted annotation.

**Threats addressed:** Prompt Injection Attacks (Output Injection Attacks)

**How:** A boolean `contains_untrusted_content: true` annotation that acts as a signal to the client that the payload requires heightened security handling, allowing the client to sanitize the payload, use indicators such as spotlighting to highlight untrustworthy content to the model, or hide that part of the response entirely.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would prefer this to be part of ToolAnnotations. But I think we can discuss that in the thread.


... add more issues here

## Next Steps
Expand Down
Loading