Menu

For application security & platform teams

Know what your agents can access—and review what changes.

Review AI agent configurations, skills, and tool definitions in one workflow. Triage changes with evidence, then enforce your team’s policy in GitHub.

Free scan. No account required. The scanner reads configuration without running your agent.

Evidence with every finding Review history for your team
Foo Guard/Acme AI Platform
TEAM WORKSPACE

Review inbox

Items that need a decision

Updated just now

Tool definition changed

release_agent · Declared by connected server · 4 min ago

CHANGED

High risk: unrestricted shell access

support-copilot.yaml · Configuration scan · 18 min ago

MAYA

New dependency update

research-agent · Reported inventory · 1 hr ago

OPEN
Assignment · Acknowledgment · Review historyMJA

Illustrative product view · Example data

Configurations & skillsTool definition changesGitHub policy checksOptional Gateway monitoring

A practical review loop

Make agent changes visible before they become hard to track.

As agents, skills, and connected tools evolve, Foo Guard gives your team a place to inspect the change, see the evidence, and decide what happens next.

01

See what’s configured

Scan agent configurations and skills for risky permissions, credentials, and approval settings. Inspect the evidence and scan coverage.

Try a free scan ↗
02

Review what changed

Compare versions and tool definitions. Bring scan findings, dependency updates, and Gateway concerns into a shared review inbox.

Explore team reviews ↗
03

Apply your policy

Run checks in GitHub and CI. Set a policy threshold and require the check in branch protection to gate merges.

See GitHub checks ↗

Evidence you can interpret

Know where each signal comes from.

Distinguish what a configuration declares from what an agent reports or what Gateway observes, so reviewers can judge each signal in context.

Configuration and skill filesScanned copy · Version fingerprint · Finding evidenceDECLARED
Agent-reported inventoryReported files and tools · Freshness shownREPORTED
Gateway request activitySupported requests routed through GatewayOBSERVED

Controls that fit your workflow

Start with review. Add enforcement where you need it.

Use the parts of Foo Guard that match your deployment process, with each control’s scope made clear.

Gate configuration changes in GitHub

Review new, existing, and resolved findings against the pull request’s base revision. Set a threshold and require the check for merges.

Learn about GitHub checks ↗

Monitor supported MCP traffic

Route supported MCP requests through Gateway to inspect allowed, flagged, and blocked activity. Team policies can enforce decisions.

Gateway covers requests routed through it. Calls that bypass Gateway are outside its coverage.

Explore Gateway ↗

Start with one agent configuration.

See the findings, inspect the evidence, and decide whether Foo Guard fits your review process.

Run a free scan