Try It turns a prepared scenario into a real policy in one click, so you can put a rule in place and then watch it fire from your own agent.
The page has two faces. Most organizations get the scenario list below. Where the policy harness is enabled, an Admin gets that instead — a browser agent with its own sandbox rules, described at the end of this page.
What’s on the page
Two further columns carry no header: one holds this row’s button, and the chevron at the end expands the row into Why it matters, Try this prompt — naming the policy it creates and its Block action — and, once created, Incidents.
A counter above the list shows how many scenarios you have created, and how many of those you have tested.
Filters and controls
There are none. The scenarios are a fixed list, shown in full.What you can do
An Analytics Viewer reads the table and the expanded detail, but gets no Create Policy or Delete button. Every scenario’s policy is created with the Block action.
The policy harness
Where your organization has it enabled, an Admin opening Try It gets a coding agent running in the browser instead of the scenario list. You write a rule, give the agent a prompt that would trip it, and watch what happens — without installing anything on a machine.The policies here are the harness’s own. They are separate from your organization’s policies and expire two hours after you last use them, so a harness result shows how a rule of that shape behaves, not what your live policies currently do. If you come back to an empty Policies list, they expired; set them up again.
/mcp add.