Agent allowlist use cases and requirements #116
Description
Per resolution: https://www.w3.org/2026/02/19-webmachinelearning-minutes.html#206a
Context seeding from @MiguelsPizza #51 (comment):
One thing to note here is that existing libraries that implement front end tool calling might want to support the WebMCP spec from a consumer (and possibly producer) standpoint.
Once we align on the client API surface, it would be worth exploring additional tools annotations that whitelist which agent can see and execute the annotated tool (browser agent, extension agent, in-page agent, iframe agent etc)
I think of this from an enterprise perspective where they might have many web apps that support WebMCP and their own internal extension to call those tools, but they don't want the tools exposed to the 1st party agent that ships with the browser.
We probably want to lift related follow-up commentary from #51 to here to focus.