AgentGate Playground

An interactive AI security playground

A helpful AI.
A watchful gate.

What happens when a document tells an AI to do something it shouldn't? Watch a separate set of rules check the action before a tool runs.

Project showcase · The interactive app runs locally.
Simulated documents and email. No real messages are sent.

AgentGate Playground: a shield and open gateway

The model proposes.
The policy decides.

A small boundary with a big job

A suggestion is not permission.

A hidden instruction in meeting notes might ask for a private member list. That is a prompt-injection attempt. Our gate does not need to trust the instruction: it checks whether the requested action is permitted.

  1. 01

    The AI proposes

    Read a document, create an email draft, or send a draft.

  2. 02

    The gate checks

    Check document access, recipient permissions, and information sensitivity.

  3. 03

    The result is visible

    Allow it, block it, or wait for a person to approve the send.

Inside the playground

See the decision. Understand the rule.

These screenshots show prepared Replay examples using the app's real policy checks. Open an image to inspect it at full size.

Blocked

A private list stays private.

The assistant can read the club notes, but it cannot open the member roster. An instruction hidden in those notes does not grant extra access.

The timeline names the rule and shows that the read tool never ran.

Replay timeline showing public notes allowed and the member roster read denied
Sensitivity matters

Same contact. Different information.

A sponsor can receive public club news, but not the confidential budget. Drafts inherit the highest sensitivity of the documents read during the session.

An approved address is not permission to receive everything.

Sensitive-information scenario comparing public and confidential data handling
Human approval

You make the final call.

When approval is required, the send pauses. A person reviews the recipient and message before deciding. The AI cannot press Approve for itself.

The result appears in a mock outbox, not a real email account.

Approval dialog showing the proposed email for human review

Two ways to explore

Replay or live AI.

Replay uses prepared proposals. It is repeatable and needs no AI service connection.

Live uses a connected model, with direct Google Gemini support. It requires your own server-side API key; access, quotas, and billing depend on your account.

Both use the same gate. Gemini adapter tests use mock responses; they are not proof of live API access.

A teaching tool, not a production gateway.

The app has three simulated tools, synthetic documents, and temporary in-memory state. Its tests do not establish a universal defense against prompt injection.

This website is a static showcase. It does not run the Python backend or collect API keys.

Python · FastAPI · React · TypeScript · Gemini

Explore the project

Open the gate. Keep the checks.