You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 51ed756
Browse filesBrowse the repository at this point in the historyBrowse files
@@ -1606,6 +1629,20 @@ This section assumes [=agents=] operate with certain baseline capabilities that
1606
1629
1607
1630
These capabilities enable powerful user experiences but also create new risks that must be addressed through a combination of protocol design, agent implementation, and user controls.
1608
1631
1632
+
Many of the risks associated with these baseline capabilities—such as indirect prompt injection from
1633
+
untrusted web content, cross-origin data correlation, and unauthorized actions within an
1634
+
authenticated session—apply broadly to any [=agent=] operating on the web on a user's behalf,
1635
+
regardless of whether a site exposes WebMCP tools. While WebMCP provides protocol-level boundaries
1636
+
and semantic hints ({{ToolAnnotations/readOnlyHint}}, {{ToolAnnotations/consequentialHint}},
1637
+
{{ToolAnnotations/untrustedContentHint}}), a malicious site can omit or misrepresent those hints.
1638
+
1639
+
Preventing an [=agent=] from being manipulated by an untrusted site or inappropriately disclosing
1640
+
cross-origin data is primarily the responsibility of the [=agent=]'s own security model rather than
1641
+
something this specification can normatively enforce. Broader standardization and guidance around
1642
+
[=agent=] identity, permissions, delegation, and web interactions are being explored in the proposed
1643
+
[Agentic Web Working Group](https://w3c.github.io/charter-drafts/2026/agenticweb-wg.html)
1644
+
[[AGENTICWEB-WG]].
1645
+
1609
1646
<h3 id="key-risks">Key Security and Privacy Risks</h3>
@@ -1973,6 +2010,24 @@ page, protecting against malicious scripts or dependencies from using WebMCP API
1973
2010
1974
2011
**How:** A boolean {{ToolAnnotations/consequentialHint}} annotation acts as a signal to the client or agent that the tool performs a consequential action, such as booking a flight or transferring money. This way they can selectively enforce mandatory user confirmation prompts before executing high-stakes tools, directly mitigating the risk of accidental or malicious misrepresentation of intent.
1975
2012
2013
+
<h4 id="mitigation-agent-level-guardrails">Agent-Level Guardrails and Best Practices</h4>
2014
+
2015
+
**What:** Deterministic and probabilistic guardrails enforced by the [=agent=] when consuming WebMCP
0 commit comments