Sentinel scans your GitHub repo for AI-agent risk, MCP exposure, prompt injection, secret exfiltration, dangerous tool permissions, and cost abuse, then shows the fix path in one dashboard.
Try the dashboard flow with a demo repo:
Root cause
The dashboard makes security obvious
User journey
The product is not a generic scanner. It is a mission-control dashboard for AI-agent security: every scan explains what can be attacked, what it can cost, who owns it, and exactly what needs to change.
Paste a repository URL. Sentinel pulls real source, detects AI agents and MCP servers, then builds a security map without asking for credentials.
The dashboard shows critical risks, tool permissions, secret reachability, cost exposure, blast radius, and attacker kill chains in one place.
Sentinel explains the root cause, recommends code and config changes, and gives your team remediation notes that map directly to the finding.
What Sentinel fixes
The dashboard categories are the marketing promise: Sentinel finds the new attack surface created by agents, tools, MCP servers, and LLM cost loops.
Guard prompts, sanitize retrieved context, and restrict tool execution.
Remove paths from agents to env vars, logs, files, and cloud tokens.
Apply least privilege across shell, filesystem, network, database, and cloud tools.
Audit MCP servers, commands, transports, tool counts, and unsafe external reach.
Add rate limits, loop controls, retry caps, and budget-aware execution paths.
Show what each agent can touch, what it can leak, and how to shrink the radius.
Everything connected
Other tools hand you isolated alerts. Sentinel stitches agent permissions, MCP servers, reachable secrets, attack paths, cost exposure, and suggested fixes into one dashboard flow.
Detect AI agents, MCP servers, tools, commands, transports, and risky capabilities.
Show critical paths from prompt to tool to secret, cloud, database, or runaway spend.
Turn each finding into least-privilege changes and remediation notes for engineering.
Replay
Surface
agent -> MCP -> tools
Owner
@platform-security
Fix
least-privilege guardrails
We do not just throw CVE names and stack traces at small teams. Sentinel turns every finding into what happened, why it matters, and what to fix first, with video walkthroughs and a voice assistant for people who do not live in security tooling.
Security Report
A short walkthrough explains the issue like a teammate would.
Ask what happened, what to fix, and what customers need to know.
Small business owners, vibe coders, and solo builders can ship a real app in a weekend. But the app still has auth, secrets, APIs, dependencies, agents, tools, and customer data.
Sentinel sits beside them like a security teammate: it scans the repo, explains the scary parts in plain English, and turns issues into fixes they can understand.
You can keep building fast without pretending you understand every security term.
Know whether the app taking payments, bookings, or customer data is safe enough to launch.
Video explanations and voice Q&A turn findings into a clear next step, not a panic spiral.
How it works
Connect → Map → Prioritize → Fix → Monitor. A buyer-friendly story backed by engineering-grade evidence.
Paste a GitHub repo. Sentinel reads real source, caches the scan, and starts mapping code, AI agents, MCP servers, tools, and dependencies.
Find every agent, MCP server, tool permission, reachable secret, external sink, and cost exposure before an attacker chains them together.
Convert raw findings into attack paths, blast radius, plain-English impact, and fix order so teams know what matters first.
Generate least-privilege hardening, prompt guards, rate limits, MCP fixes, and PR-ready remediation notes that engineers can review.
Track scan health, critical risk count, fix progress, upcoming scans, and regressions across every repo.
The AI Security Team
These are the risk lanes visible in the product: prompt injection, secret exfiltration, MCP exposure, tool permissions, and cost abuse.
Malicious instructions hidden in user input
Finds where LLM prompts trust untrusted text, tool results, or retrieved context. Then adds guardrails, validation, and safer prompt boundaries.
Agents and tools that can reach keys
Maps every path from an AI agent to environment variables, files, logs, and cloud credentials. Then reduces access and patches unsafe reads.
Model Context Protocol servers with risky reach
Discovers MCP configs, commands, transports, and tools. Then shows which servers can touch shell, files, databases, network, cloud, or secrets.
Over-powered agents before they become incidents
Builds a blast-radius view of each agent: filesystem, database, network, email, shell, cloud, and secrets. Then suggests least-privilege fixes.
Runaway LLM usage and missing rate limits
Models current and worst-case monthly spend when agents can loop, retry, or be abused. Then adds caps, throttles, and safer execution paths.
Dashboard surfaces
What is risky, why does it matter, and what should we fix first?
Let builders ask what a finding means, what to fix first, and how to explain the risk to a customer or client.
Track scan health, fix progress, recent scans, upcoming runs, and critical risk count from one calm owner-ready view.
Run a repo scan that maps AI agents, MCP servers, attack paths, blast radius, and cost exposure like a mission control panel.
One product, three clear views
Sentinel translates the same scan into a Copilot mission view, a deep agent-security graph, and a breach/fix workflow.
The top-level mission control view: repo input, plain-English report, pulse chart, risk KPIs, heatmap, and cost exposure.
The deep technical view for engineering: agents, MCP servers, capabilities, attack graph, blast radius, and remediation report.
The proof-and-repair view: show the attacker path, explain the impact, then move directly into prioritized hardening.
Sentinel is built for the people actually shipping the product: founders, freelancers, vibe coders, agencies, and small teams. It explains each issue like a patient teammate, then turns the fix into a short action list.
Sentinel Assistant
Ask anything about the report
Run a repo scan, watch the explanation, ask the assistant what it means, and fix the dangerous paths before launch.