-
Notifications
You must be signed in to change notification settings - Fork 18
Open
Labels
Description
Currently the explainer says that tools can only exist on the top-level browsing context here. Maybe that makes things easier to reason about from a security perspective but also seems unnecessarily limiting. There's a couple of interesting use-cases to think about:
- A page which embeds an Agent, came up on Clarifying the scope of the proposal #43 (comment). If the site doesn't want the Agent to run script in the first party context, they could embed it in a cross-origin iframe instead.
- An Agent which embeds a cross-origin and wants to access it's WebMCP functionality.
We'd likely need a security policy to allowlist which origin can see a site's WebMCP functionality. I'm not sure how granular it needs to be, this origin can see all tools or a subset of tools etc.
For now, let's resolve on adding this use-case to our scope.