← All workshopsRead A Valid Token for Which Service?

Agent Guardrails and Secure Development

Keep a credential at its intended service

BOTIE

Check the verified claims against issuer, audience and current time.
Ready to test
0 passed · 0 failed · 3 not run

An empty floor. Start with the information your machine needs.

Received result

Your answer will arrive here.

Examples, experiments and workspace controls
Live values

Connect a tool's inputs to see what it produces. You can try a branch before connecting it to Result.

Try your own inputs

Use a copy of the example to try your own data. Keep the problem's assumptions in mind, and predict the effect of a change before checking the output. You can also add another branch to compare two ways of doing the calculation.

Start at an output arrow, then click or drag to an input. Drag empty space to pan. Delete removes a selection. Ctrl/Cmd+Z undoes a change.
Context for this challenge

Check the verified claims against issuer, audience and current time.

The manuals API requires a current verified token and the manual:read scope.

Inspect the component calculation
Check verified token claims(
  Verified claims or null: Verified claims or null
  Server policy: Server-owned policy
  Current time: Current time
)
Examples and results
Verified claims or null
{
  "issuer": "company-id",
  "audiences": [
    "manuals-api"
  ],
  "subject": "user-7",
  "expires": 100,
  "scopes": [
    "manual:read"
  ]
}
Server-owned policy
{
  "issuer": "company-id",
  "audience": "manuals-api",
  "requiredScope": "manual:read"
}
Current time
50
Required result
true
Verified claims or null
{
  "issuer": "company-id",
  "audiences": [
    "manuals-api"
  ],
  "subject": "user-7",
  "expires": 100,
  "scopes": [
    "manual:read"
  ]
}
Server-owned policy
{
  "issuer": "company-id",
  "audience": "manuals-api",
  "requiredScope": "manual:read"
}
Current time
100
Required result
false
Verified claims or null
{
  "issuer": "company-id",
  "audiences": [
    "manuals-api"
  ],
  "subject": "user-7",
  "expires": 100,
  "scopes": [
    "manual:list"
  ]
}
Server-owned policy
{
  "issuer": "company-id",
  "audience": "manuals-api",
  "requiredScope": "manual:read"
}
Current time
50
Required result
true
Try a fresh construction

This clears this draft, including its undo history. Earlier successful attempts stay recorded. Build again without opening hints to record an independent attempt.

Stuck? Inspect a worked construction

The tools below form one possible solution. You can assemble it, follow its signals, and undo that change to return to your own construction.

Assumptions and test precision

These are invented records and deterministic policy checks. The browser runs no agent, shell command, MCP server or network request. Passing these fixtures establishes only the stated policy behaviour. Numerical tests allow a difference of 0.001. Lists and structures must also have the right shape.

Your last tested pieces can start the full construction. An existing draft there keeps its own pieces.

The trusted verifier returned no claims

This check uses the pieces from “Check token and scope before the object”.

BOTIE

Token validation failed before this policy ran. Claims are null. Predict the route without substituting a session ID for authentication.
Verified claims or null
null
Server-owned policy
{
  "issuer": "company-id",
  "audience": "manuals-api",
  "requiredScope": "manual:read"
}
Current time
50

Use a number, text, or an array matching the requested result. For a matrix, put each row in brackets. Saving your prediction runs your current construction on these inputs and checks the earlier examples too.

Build a construction in the workspace above first. This case will test those pieces.

Where does your application turn untrusted token bytes into verified claims?

Keep cryptographic verification and application policy separate, with both enforced.

These are invented records and deterministic policy checks. The browser runs no agent, shell command, MCP server or network request. Passing these fixtures establishes only the stated policy behaviour.

Work through the Python challenges →
Continue the courseWhat Exactly Did the Person Approve? →
← What Did We Actually Trust When We Connected the MCP Server?