Fyver Interceptor

Your AI agents are powerful.
Now make them governable.

Fyver Interceptor is the security layer for enterprise AI agents. For business: deploy AI with every agent action governed and every decision auditable. For engineers: one hook per dispatcher, sub-50ms p99 allow/deny/escalate decisions, zero agent rewrites.

<50msp99 decision latency per call
3Decisions: allow / deny / escalate
6Compliance frameworks mapped
100%Decisions hash-chained & auditable

AI agents are your fastest employees.
And your least supervised.

They issue refunds, change records, and touch customer data — at machine speed, with no human in the loop. One bad tool call is a breach, a lawsuit, or a headline. Fyver is the supervision layer.

RISK

Agents act without guardrails

An AI agent with a refund tool and no spending limit is a liability. Traditional IAM wasn't built for agents that reason, plan, and improvise.

ANSWER

Policy at the interception point

Fyver sits between your agents and their tools. Every call is checked against your policies in milliseconds — allow, deny, or escalate to a human. No code changes to your agents.

PROOF

Evidence auditors accept

Every decision is hash-chained into a tamper-evident log, mapped to SOC 2, ISO 27001, EU AI Act, and NIST AI RMF controls. Compliance evidence writes itself.

One check. Every call. <50ms p99.

For the technical team: a single hook in your agent's dispatcher. Your agents stay untouched; decisions return in milliseconds.

AI AGENT SIDE TRUST BOUNDARY ENTERPRISE SIDE AI Agent Agentforce · ServiceNow AI any agent tool call Fyver Interceptor Policy engine · <50ms p99 allow / deny / escalate never executes business logic allow MCP Server hosts the tools executes the call Enterprise Data Salesforce · ServiceNow Oracle · any system ✕ DENY ⏸ ESCALATE Human approval one-time grant 🔔 Notifications email · Slack · ITSM · webhook ⛓ Audit ledger (hash-chained) Runs anywhere Docker runs — OCI · AWS · Azure · Google Cloud · on-prem

Live example — a $4,000 refund intercepted in 38ms:

Refund Concierge issue_refund $4,000 Fyver Interceptor P-01 · 38ms amount 4000 > 500 ⏸ ESCALATE Human approval one-time grant
$ agent → salesforce.issue_refund { amount: 4000 }
→ Fyver check(agt_sf_029, issue_refund, …)
→ P-01 matched: amount > 500 → ESCALATE
→ human approves → one-time grant issued
$ agent retries → ✓ ALLOWED (grant consumed)
 
$ agent → servicenow.delete_incident
→ P-18 matched → ✕ DENIED — no policy allows deletes
01

Agent acts

Your AI agent — in Salesforce, ServiceNow, or any platform — attempts a tool call. A one-line hook sends the agent ID, tool name, and arguments to Fyver.

02

Fyver decides

Policies evaluate in priority order. First match wins: allow, deny, or escalate to a human. Every decision records its full reasoning chain.

03

Everything is proven

Each decision lands in a hash-chained audit log. Tamper with one entry and the chain breaks — verifiable by anyone, anytime. Compliance evidence writes itself.

Two stories. One platform.

Buying and building are different jobs. The demo follows two people.

Sarah — business executive
THE BUSINESS CASE

Meet Sarah

Business executive. Her company is deploying AI agents — her question: "Who's watching the agents?" Follow her story (~2:50): interception, approval, audit, drift.

▶ Watch Sarah's story

David — platform engineering
THE PRODUCTION PATH

Meet David

Platform engineering. Hundreds of actions, dozens of agents — his standard: "One command. No rewrites." Follow his story (~2:00): CLI, hidden flows, deep dive.

⌨ See the CLI

From bare code to guarded agent.
One command.

The production path. Point the CLI at your existing code — it generates the guardrail wrapper, deploys it, and stages the policies. Your code never changes; the console has the final say.

$ ./fyver auth login
→ approve in your browser — no password, no pasted session cookies
✓ Authorized. Token saved to ~/.fyver/credentials.json
 
$ ./fyver wrap -p salesforce-flow -i ./flows -a agt_sf_031 -o ./out \
    --deploy --import-policies
→ My_Support_Flow → My_Support_FlowFyverWrapper.flow-meta.xml (2 inputs)
→ Deployed: Succeeded via Metadata API (+ guard class bundled)
→ Imported 2 polic(ies) as DISABLED — review and enable in console
01

Generate

Wrappers are built alongside your code — Apex classes, Flow XML, ServiceNow Script Includes. The original is never modified. Generated code holds no secrets: tokens are read from your platform's protected storage at runtime.

02

Deploy

Push straight to the platform — Metadata API for Salesforce, Table API for ServiceNow. Direct from the CLI, straight to production.

03

Review, then enforce

Suggested policies land disabled. You review them in Policy Studio, tune the thresholds, and enable — the CLI suggests, the console decides.

Validated where your agents live.

Three enforcement points, each tested end to end — deny blocks, escalate pauses for a human, allow passes with a one-time grant. Plus a native MCP endpoint for everything else.

SALESFORCE

Apex actions

Your @InvocableMethod classes get a thin wrapper with the guardrail built in. One-line check, token from protected custom metadata, deploy from the console or the CLI.

✓ End-to-end validated

SALESFORCE

Flows

Autolaunched flows — including Salesforce-provisioned templates the APIs can't even see — wrapped, deployed as Draft, activated by you. Tested live against a real template flow.

✓ End-to-end validated

SERVICENOW

Script Includes & agents

Dispatchers guard every tool call; deny, escalate, and auth failures all throw fail-closed. Table API deploy, one-command token sync when credentials rotate.

✓ End-to-end validated

See it in action

Follow Sarah's story (~3:00) or David's (~2:00) — or explore any of the 19 functional chapters.

▶ Watch the demo

Built for the enterprise

Production-grade controls for teams that answer to auditors.

📊

360° dashboard & live stream

Tool calls inspected, policy blocks, approvals waiting, drift alerts — the health of your agent fleet at a glance, with a live event stream underneath showing every decision as it happens.

🛡️

Policy studio

Write rules in plain language: who can do what, under which conditions. Templates for common cases, a simulator to prove rules work before deployment, full version history with one-click rollback.

⚡

Real-time interception

Sub-50ms p99 decisions on every tool call. In-memory policy engine, pre-compiled patterns, pooled database connections — the policy check adds no perceivable latency. One-line hooks for Salesforce Apex and ServiceNow Script Includes — deploy from the console with a single click.

👤

Human-in-the-loop

Escalated calls pause for human judgment. One-time grants mean an approval works exactly once — replay-safe by design. The control auditors ask for by name.

🔍

Drift detection

Two layers: tool definitions are hash-pinned at sync time (interface changes), and source code — Salesforce Apex classes, ServiceNow Script Includes — is hashed too. If someone edits a helper to bypass the check, you know.

📋

Tamper-evident audit

Every decision hash-chained to the previous one. Verify the chain in one click; export the full log for external review. Evidence that proves itself.

🗄️

Retention by design

Hot / warm / cold data tiering keeps queries fast as you scale: recent events live, older ones archived, audit exports signed and chain-verified. Built for SOC 2, ISO 27001, and GDPR — the audit log is never deleted.

🔐

Authenticated enforcement

Every enforcement call is token-authenticated between your platforms and the console. Every decision arrives over a secured channel, from a verified caller.

🔒

Secrets encrypted at rest

SSO client secrets, OAuth tokens, and platform credentials are Fernet-encrypted in the database. Backups are automated daily with verified restore drills.

🔌

MCP-native

A real MCP server endpoint (/mcp) — any MCP client connects via JSON-RPC, lists governed tools, and has every tools/call checked against your policies. Vendor-neutral by protocol.

🌐

Cross-platform, one policy layer

Salesforce Apex, Salesforce Flow, ServiceNow, and any MCP client — governed by the same policies, the same approval queue, the same audit trail. Add a platform without rebuilding governance.

🏗️

Adapters & environments

Dev, test, and prod environments per adapter. Promote policies through environments with full version history — what runs in prod is exactly what you tested.

👥

Caller roles (RBAC)

Policies match on who is driving the agent, not just which agent. A support agent's $4,000 refund is denied; a manager's is escalated. Same tool, different human, different decision — fail-closed by design.

🔐

Enterprise SSO

Sign in with Okta or Microsoft Entra ID via OIDC (Google Workspace also supported). IdP groups sync to caller roles automatically on every login — join the Fyver-Managers group, get the support_manager role.

🔔

Notifications

Escalations push to email, Slack, PagerDuty, or open a real ITSM ticket with the approve link inside. Smart dedup keeps every alert meaningful — one per event.

🚀

One-click deploy hooks

Push the interceptor to Salesforce or ServiceNow from the agent card. Seven Apex classes via the Tooling API, three Script Includes via the Table API, upserted by name. Deploy history shows exactly what changed, per file.

⌨️

CLI for production

From bare code to guarded agent in one command: ./fyver wrap generates the wrapper alongside your code, deploys it, and stages suggested policies as disabled for your review. The production path for platform teams.

🌊

Salesforce Flow guardrails

Autolaunched flows — including Salesforce-provisioned templates the APIs can't even see — wrapped with the same guardrail. Ten lines of XML, deployed as Draft, activated by you.

⚡

Bulk approval

Select-all, approve-all, deny-all. When a load test (or a real incident) floods the queue with thousands of escalations, clear them in one click — with the same audit trail as individual decisions.

🛠️

Console ops

Backups, retention jobs, and schedules — all from the console. One-click pg_dump with download, retention dry-run and live run, daily schedules with last-run status. Everything runs from the browser.

Compliance with live evidence

Six frameworks mapped to live system data. Click any badge in the console to see the exact controls and their real-time status — live data, always current.

SOC 2Trust Services Criteria
ISO 27001Annex A controls
EU AI ActHigh-risk AI obligations
NIST AI RMFGovern · Map · Measure · Manage
GDPRPrivacy by design
Internal AI PolicyYour rules, enforced

Ship AI agents your auditors will love.

Join the beta. We'll get you from zero to governed in one session.

Or email us directly: contact@fyver.ai