5/23

5 of 23

A WebMCP consent demo

Built for the WebMCP ChallengeDemo data

Field-level consent for WebMCP

Fill the form. Keep the rest.

This form needs five profile fields and a yes/no age check. You review every request before anything is filled.

23

profile fields

5

needed by the form

18

not needed by the form

Demo profile

23 fields on file

5 needed

01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19
20
21
22
23

Current state

consent:v0 · state:v1

Birth date is checked, never added to the form.

Cooling kit application
Six answers are needed. This demo never submits the form.
0/6
Answers added0%
x
1

Legal name

Shown on the completed form.

2

18 or older

A yes/no check is enough. Birth date is not needed.

3

Country of residence

Applicants must live in the eligible country.

4

Municipality

Used to send the request to the right local office.

5

One contact channel

Email or phone. Only one is needed.

6

Household size

Used to choose the right kit size.

Birth date is never added to the form
Requests to review
Each field stays hidden until you approve it.
0 of 5 approved

Age check

Confirm 18+ without sharing a date of birth.

No requests yet

Let the agent ask for the five fields the form needs, or try it here.

Demo profile · 23 fields

Hidden in the UI until approved

0 requests to review5-field limit: 0/5
Page tools
WebMCP tool examples

Checking WebMCP

Looking for the browser's WebMCP API.

get_application_staterequest_disclosure
Activity log
Tool names and results only. Field values are not logged.

No tool calls yet

Run the demo with the browser agent to see recent calls.

policy

01:00:00 AM

Synthetic vault loaded locally. No field values released.

Run it with an agent
Open this page in a WebMCP-capable browser and give the agent this prompt.
Demo prompt

“Fill this demo form with as little data as possible. Use the 18+ check instead of requesting the birth date. Ask for the five fields you need, wait for my approval, then fill only the approved fields. Leave final review to me.”

01

Read the form

The agent gets six requirements from the page tools.

02

Ask first

You approve each field before it can be filled.

03

Change your mind

Remove a field and the old tool stops working.

Checks in this build
Four behaviors covered by the local demo and test suite.
23 → 5

Only the needed fields

Five profile fields complete five answers; age is checked separately.

0

No profile values before approval

Tests scan safe engine and WebMCP responses; demo fixtures remain in the public client bundle.

stale

Old tools stop working

Removing a field changes the consent version, so the previous apply tool is rejected.

manual

Final review stays in the UI

There is no WebMCP tool that approves or submits the completed form.