Repository Issue Activity (beta)

#300 Clarify that unregistration must not fail an in-flight execution

#298 §6.4: add page-enforced write boundaries as a mitigation for agent over-reach

#199 Frameworks and WebMCP Meta Issue

#312 Keeping the agent in-sync with the page's context

#262 WebMCP loses important context when tools appear or disappear

#196 WebMCP tool execution progress report

#227 Tool discovery should not be limited to a single traversable navigable

#273 WebMCP internationalization review checklist

#272 WebMCP accessibility review checklist

#106 Supporting interoperable probabilistic defense structures through shared attack eval datasets

#207 Support developer tooling

#252 Hosting official polyfill for WebMCP

#74 WebExtensions API to enumerate and invoke tools

#178 Please formally document Permissions-Policy: tools=() as a security control

#303 Tool aliases

#255 Tool collections: coarse-grained grouping with progressive disclosure

#165 WebMCP elicitation via requestUserInteraction() (was: Human in the Loop support for non-browser clients)

#182 How to expose failed declarative tool registration

#96 Proposal: [Section 3] Address agent-to-tool trust — identity, scoped permissions, and delegation context

#299 Let a tool deliver a final result on caller abort

#308 Preserve what a tool already produced across the execution boundary (unifies #282, #299, #300)

#161 Proposal: Skills — workflow-level context for tool composition

#277 Define accessibility requirements for WebMCP user-agent UI

#65 WebMCP accessibility considerations

#282 No structured way to signal a tool's refusal, distinct from success or a schema-validation error