Governance · 8 min
How teams actually control what AI agents can accessRead →Security
Agents get a door, never a spare key
Your upstream credentials never leave Elva. Every tool call is identified, scoped, redacted, throttled, and logged. This page is written for the person who has to sign off on that.
Elva is a product of Theneo. The certifications, security contact, and DPA on this page are issued to Theneo and cover the infrastructure Elva runs on. The same entity name appears on the report when you request it.
5CHECKS BEFORE YOUR API
0UNSCOPED TOOLS ALLOWED
EveryCALL LOGGED, NO SAMPLING
SecondsTO REVOKE A KEY
01Request path
Five checks on every MCP tool call, in order, fail closed
Nothing reaches your API until identity, scope, redaction, rate, and audit have all passed. A failure at any step denies the call and records why. There is no bypass path and no unscoped mode. It is what makes the governed MCP servers Elva generates safe to hand to a partner.
EVALUATING A TOOL CALLget_payment_status · Claude Desktop
01IdentityOAuth2 token or managed key, resolved to a named agentpass
02Tool scopeIs this key allowed to call this specific toolpass
03Field redactionPII and internal fields stripped per contractpass
04Rate and quotaPer key and per tool, retry storms containedpass
05Audit recordActor, tool, arguments hash, latency, outcomepass
DECISION LOG
✓identity: agent claude-desktop, key ...8f2a
✓scope: read:payments present
✓redaction: customer_email removed
✓rate: 41 of 600 per minute
✓audit: written, 98ms, allowed
02Data handling
What we store, and what we never see
Elva reads your code to derive specs; it does not need your production data. Request and response bodies are not retained by default, and PII fields are redacted at the gateway before they reach an agent.
Source code access is read-only and scopedA least-privilege app installation on the repos you choose. We read routes, handlers, and types. No write access, no other repos.
Bodies are not retained by defaultLogs record the tool, actor, arguments hash, latency, and outcome. Full payload capture is opt-in, per contract, with its own retention.
Encrypted in transit and at restTLS 1.3 everywhere, AES-256 at rest, per-tenant isolation. Private cloud installs can use your own KMS keys.
Your credentials stay in the gatewayUpstream API secrets live in Elva’s vault, never in an agent config or a partner machine. Rotate without redistributing anything.
03Posture
Compliance, and who holds what
The controls a security review asks for before it will approve an MCP server, with our status against each one and the entity it is issued to. Ask us for the pack and we will send it with dates attached.
CONTROLSTATUSNOTES
SOC 2 Type IIcertifiedHeld by Theneo, covering the infrastructure Elva runs on. Report under NDA.
ISO 27001 / 27701certifiedInformation security and privacy management, held by Theneo. Certificates on request.
GDPRcompliantDPA available, EU data residency on request
EncryptionTLS 1.3 / AES-256In transit and at rest, per-tenant isolation
SSO / SAML and SCIMavailableEnterprise plans, your IdP owns publish rights
Penetration testingannualThird-party, summary shared under NDA
Vulnerability disclosureopenhello@theneo.io, one business day response
Data residencyconfigurableRegional hosting, private cloud, or on-prem
04When something goes wrong
Revoke in seconds, explain in minutes
One click kills a key, an agent, or a whole server, and the log keeps everything it did up to that moment. That is the difference between an incident and an unanswerable question.
Instant revocationKeys, agents, and servers can be killed independently. In-flight calls are cut, not drained.
Anomaly alertsError-rate spikes, scope escalation attempts, and retry storms page you before a partner notices.
Forensics on demandFilter the full log by agent, key, tool, or outcome, and export to your SIEM as JSON, CSV, or webhook.
Report something to hello@theneo.io. We respond within one business day and credit every valid finding.
FAQ
How does Elva secure agent calls?
Five ordered checks on every tool call: identity (OAuth2 token or managed key resolved to a named agent), tool scope, field redaction per contract, rate and quota, and an audit record.
Does Elva expose my API credentials to agents?
No. Upstream credentials stay in the gateway. Agents hold scoped keys that can be limited per tool and revoked instantly, one key per consumer.
What ends up in the audit log?
Every call records the actor, the tool, an arguments hash, latency, and the outcome, queryable per key and per tool.
How do I report a security issue?
Email hello@theneo.io. Reports get a response within one business day.
- SOC 2 Type II · certified
- ISO 27001 / 27701 · certified
- GDPR · compliant
- Encryption · TLS 1.3 / AES-256
- SSO / SAML and SCIM · available
Send this page to your security team
They will ask about scopes, logs, residency, and revocation. All of it is answered here.