Host-controlled WebMCP access between iframes
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- html
- 领域
- api
调研方向
Start by reading the WebMCP permission model, especially how exposedTo and fromOrigins currently govern cross-origin tools; the issue does not name specific files or tests. Decide whether hosts should be able to delegate separate provider and consumer capabilities, and define how providers opt into host-authorised exposure. Done means the permission and provider opt-in model supports the described iframe topology without requiring apps to know the agent origin.
由索引模型根据 Issue 内容生成。
描述
Consider a host application that composes several cross-origin applications in iframes, with one iframe containing an agent:
Host
├── Agent iframe
├── App A iframe
├── App B iframe
└── App C iframe
Apps A–C may expose WebMCP tools. The host wants the agent to use those tools, but does not necessarily want the apps to discover or invoke tools exposed by other frames.
The host therefore wants to define a topology like:
| Frame | Expose tools | Use tools |
|---|---|---|
| Agent | no | yes |
| App A | yes | no |
| App B | yes | no |
| App C | yes | no |
The current model seems awkward for this use case because cross-origin access relies on providers and consumers knowing each other's origins through exposedTo and fromOrigins.
In a composed application, the embedded apps may not know or care which agent implementation the host uses. The host is the component that knows the intended relationship between the frames.
Would it make sense to separate the current tools permission into two independently delegatable capabilities, conceptually:
<iframe src="https://app.example"
allow="tools-provide">
<iframe src="https://agent.example"
allow="tools-consume">
This would let the embedding host decide which frames may expose WebMCP capabilities and which frames may consume them.
There would probably also need to be a way for a provider to opt into host-authorised exposure, rather than having to enumerate every possible consuming agent origin.
This seems particularly useful for host applications that compose independent first- and third-party web applications alongside an embedded agent.
- 主要语言
- Bikeshed
- 星标
- 4.7k
- 派生
- 328
- 平均合并
- 2 天 9 小时
- 30 天内合并 PR
- 15
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
webmachinelearning/webmcp 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
webmachinelearning/webmcp#362 ·
维护者通常 1 天内回复
-
难度 1/5 1-3 小时 新手友好度 72/100
webmachinelearning/webmcp#360 · 1 条评论 ·
维护者通常 1 天内回复
-
Say how an agent should weigh annotations that the page wrote about itself可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
webmachinelearning/webmcp#353 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 67/100
webmachinelearning/webmcp#343 · 1 个 reaction ·
维护者通常 1 天内回复
-
Agenda+ i18n-tracker
难度 2/5 1-3 小时 新手友好度 75/100
webmachinelearning/webmcp#273 · 3 条评论 ·
维护者通常 1 天内回复
查看 webmachinelearning/webmcp 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 70/100
restatedev/sdk-typescript#813 ·
-
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 72/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
Merit-Systems/x402scan#1312 ·
-
type:bug
难度 2/5 1-3 小时 新手友好度 78/100
Azure/apiops-cli#331 ·
维护者通常 3 天内回复