Scan agent inputs and tool calls before they turn into action.
Armorer Guard is the local inspection layer for agent runtimes. It helps catch prompt injection, credential leakage, exfiltration attempts, and dangerous tool calls at the boundary where text crosses into execution.
Inspect a tool call
$ armorer-guard mcp-proxy -- npx your-mcp-server
{
"policy_action": "dangerous_tool_call",
"confidence": "high",
"sanitized": true
}
Live scanner
Use the advanced Guard surface.
Tune the surface, trace stage, scope, tool, and threshold to test how Guard behaves at different agent boundaries.
armorer-guard inspect-json
Native scanner surface
Input
Preset or paste text at the agent boundary.
Surface
Stage
Verdict
Ready
Confidence
n/a
Latency
n/a
Runtime
waiting
Reasons
Semantic Scores
Boundary Context
Run a scan to see Guard's sanitized text and structured policy output.
Where Guard fits
Put policy at the execution boundary.
Prompt-only defenses are brittle. Guard is designed for the places where agent text can influence commands, files, tools, logs, memory, and outbound messages.
Inspect untrusted text
Scan web pages, documents, tickets, chat messages, retrieved snippets, and model output before they enter agent context.
Gate risky actions
Evaluate tool-call arguments before shell, filesystem, browser, SaaS, or MCP actions can become system changes.
Return structured policy
Use JSON results with sanitized text, reasons, confidence, and policy labels inside an orchestrator or control plane.
Detection coverage
Signals Guard can flag.
These checks are useful by themselves, and stronger when paired with Armorer runtime controls for sandboxing, credentials, approvals, and audit trails.