Drop the stale native-agents note from the security questionnaire - #269
Open
lazizbekravshanov wants to merge 1 commit into
Open
Drop the stale native-agents note from the security questionnaire#269lazizbekravshanov wants to merge 1 commit into
lazizbekravshanov wants to merge 1 commit into
Conversation
There was a problem hiding this comment.
Pull request overview
Updates the security/privacy questionnaire to align with the current WebMCP spec wording around exposedTo, removing an outdated aside about native-agents from earlier design discussions.
Changes:
- Removes the stale parenthetical about
native-agentsin theexposedTodescription. - Keeps the questionnaire statement focused on the current spec behavior: origins control tool discovery.
馃挕 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| The feature is gated by the [`"tools"`](https://webmachinelearning.github.io/webmcp/#permissiondef-tools) permission policy. It is allowed in top-level documents and same-origin descendants by default; The permission policy can be used to allow it in cross-origin iframes and/or to disallow it in same-origin frames. | ||
|
|
||
| Additionally, tools can specify [`exposedTo`](https://webmachinelearning.github.io/webmcp/#dom-modelcontextregistertooloptions-exposedto) to control which origins (or `native-agents`, name to be bikeshed per [#179](https://github.com/webmachinelearning/webmcp/pull/179)) can discover them. | ||
| Additionally, tools can specify [`exposedTo`](https://webmachinelearning.github.io/webmcp/#dom-modelcontextregistertooloptions-exposedto) to control which origins can discover them. |
Contributor
|
anssiko marked as non substantive for IPR from ash-nazg. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The security questionnaire says
exposedTocontrols which origins (ornative-agents, name to be bikeshed per #179) can discover tools. That parenthetical looks stale: #179 merged in May 2026,native-agentsdoes not appear anywhere else in the repo or in the spec, and the spec today restrictsexposedToto potentially trustworthy origins only. This drops the parenthetical so the questionnaire matches the spec.