Guidance for sensitive form fields (credentials, card data, national IDs) in declarative and imperative tools
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 48/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- html
- 领域
- security
调研方向
Read the declarative API and security guidance, then review related issues #110 and #313 and the linked country-packs design notes. Compare the proposed autocomplete exclusions, agent handoff hint, and security guidance against the spec's existing tool schema. Done means a concrete direction is agreed on and the spec explains how sensitive form fields are handled.
由索引模型根据 Issue 内容生成。
描述
Problem
Neither the spec nor the Chrome security guidance says how sensitive fields should be handled when a form becomes a tool. The declarative API builds inputSchema from every named control, so a checkout form exposes card number and CVV, and a login or KYC form exposes one-time codes and national ID numbers, as agent-fillable parameters.
Browser agents already treat these fields specially: Claude in Chrome, Gemini in Chrome and OpenAI's agent hand passwords, OTPs and payment details back to the user rather than passing them through the model. Tool schemas currently give them no way to know which parameters those are.
Evidence
- PCI DSS v4.0.1 Req 3.3.1: Sensitive authentication data (CVV, PIN) must not be retained after authorization. We treat agent transcripts as retention.
- NIST SP 800-63B, PSD2 SCA-RTS Art. 4 and RBI's 2025 authentication directions treat one-time codes as authentication factors held by the user.
- Several jurisdictions restrict processing of national ID numbers: National laws under GDPR Art. 87, UIDAI rules for Aadhaar, and Singapore's PDPC NRIC guidelines.
In auto-webmcp (an open-source library that turns forms into WebMCP tools) we now exclude these fields from the schema, list them in the description, and set consequentialHint. Design notes: https://github.com/prasanna-gyde/auto-webmcp/blob/main/docs/design/country-packs.md
Possible directions
- Declarative API: By default, exclude controls whose
autocompleteiscc-number,cc-csc,cc-exp*,one-time-code,current-password,new-passwordorwebauthnfrom the generated schema. - Signal to agents: A per-parameter hint (for example
x-user-input: true, or a list on the tool) meaning "the user completes this field", so agents hand off instead of guessing or asking for the value in chat. - Security considerations: A short section recommending that tool results not echo credentials, card data or hidden inputs.
Related: #110 (sensitive tool outputs; a comment there raises the input direction this issue covers) and #313.
Happy to contribute text or test cases.
- 主要语言
- 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 小时 新手友好度 78/100
CodeChefVIT/ffcs#281 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
priority-p0 program:egi role:B stage:beta task
难度 2/5 1-3 小时 新手友好度 65/100
rrahimi-uci/caliber-suite#696 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
blocklist addition
难度 1/5 1 小时以内 新手友好度 72/100
MetaMask/eth-phishing-detect#305800 ·
维护者通常 1 天内回复