Post-deploy discovery
Scans find risk hours or days later. An agent with write tools can cause material harm in seconds.
- Rail: pre-act intercept on tool/MCP calls
security.alphagentic.io · Guardrail Protocol v0.1
Tenable-class tools excel at finding exposure after the fact. Agentic systems need a different center of gravity: lanes, tools, gates, and reasoning — not only CVE lists.
Pre-act evaluation · Semantic + schema layers · Evidence ledger · Continuous adversarial evals
Respectfully: Tenable and peers are strong at asset/CVE/cloud exposure. Agentic risk is primarily action-time capability, not unpatched packages.
Scans find risk hours or days later. An agent with write tools can cause material harm in seconds.
Hosts and CVEs dominate. Dangerous unit is the edge: agent → tool → data class → blast radius.
Exact-match filters lose to paraphrase, encoding, and indirection — a known AI control failure mode.
Risk scores rank findings. Runtime needs “should this agent do X now?” with a traceable why.
Agents inherit broad credentials; toxic combinations form outside human IAM workflows.
Tickets close CVEs; few programs continuously red-team agent behavior in production paths.
A simple contract: every privileged act is evaluated, explained, and ledgered.
Each agent gets a lane: purpose, tool allowlist, data classes, environment (sandbox/prod), human gate rules.
Before tool/MCP/API execution, submit Action Intent: agent id, tool, args schema, context, urgency.
Allowlist → lane boundary → data class → blast radius → semantic intent → optional human escalate.
ALLOW · DENY · ESCALATE. Every outcome includes structured reasons and policy version.
Immutable record for audit: who/what/when/why. Exportable for compliance — not a PDF afterthought.
Adversarial suites (injection, exfil, scope creep) run like CI — guardrails that aren’t tested don’t exist.
Pick a lane and an attempted action. Rail returns a decision with reasoning layers. (Illustrative client-side demo.)
Not “more dashboards.” A tighter loop from policy to proof.
| Layer | Tenable-class center | Rail center |
|---|---|---|
| Inventory | Assets, CVEs, cloud resources | Agents, lanes, tools/MCP, data classes, policies |
| Time | Scan / expose / remediate cycles | Milliseconds before action + continuous eval |
| Decision | Risk score & priority queue | ALLOW / DENY / ESCALATE + structured why |
| Identity | Human-first IAM + some NHI signals | Non-human lanes as first-class least privilege |
| Proof | Findings & reports | Immutable action ledger & policy versioning |
| AI abuse | Emerging posture / exposure views | Semantic + schema guardrails on the wire |
POST /v1/evaluate
Submit intent; receive decision + reasons + ledger id. Wire into agent runtimes and MCP proxies.
Policies ship as signed packs. Roll forward/back. Every decision cites pack version.
One stream for SecOps, GRC, and incident review — not three tools stitched by screenshots.
Honest scope. Ship the control plane before the marketing fleet.
This site. Decision model. Gap thesis. Design system aligned to AlphAgentic craft.
Server-side policy engine, MCP/tool proxy, signed ledger, sandbox agent fixtures.
IdP, SIEM export, ticketing, continuous eval CI, multi-tenant control hub.
security.alphagentic.io — AlphAgentic Rail
Talk to us