MCP Server Security and Compliance: SOC 2, ISO 27001 · Evlio

Security
Agents
get
a
door,
never
a
spare
key
Your upstream credentials never leave Evlio. Every tool call is identified, scoped, redacted, throttled, and logged. This page is written for the person who has to sign off on that.
Evlio is a product of
Evlio
.
The certifications, security contact, and DPA on this page are issued to Evlio and cover the infrastructure Evlio runs on. The same entity name appears on the report when you request it.
Request the security pack
Enterprise options
5
CHECKS BEFORE YOUR API
0
UNSCOPED TOOLS ALLOWED
Every
CALL LOGGED, NO SAMPLING
Seconds
TO REVOKE A KEY
01
Request 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
Evlio generates safe to hand to a partner.
EVALUATING A TOOL CALL
get_payment_status · Claude Desktop
01
Identity
OAuth2 token or managed key, resolved to a named agent
pass
02
Tool scope
Is this key allowed to call this specific tool
pass
03
Field redaction
PII and internal fields stripped per contract
pass
04
Rate and quota
Per key and per tool, retry storms contained
pass
05
Audit record
Actor, tool, arguments hash, latency, outcome
pass
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
02
Data handling
What we store, and what we never see
Evlio 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 scoped
A 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 default
Logs 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 rest
TLS 1.3 everywhere, AES-256 at rest, per-tenant isolation. Private cloud installs can use your own KMS keys.
Your credentials stay in the gateway
Upstream API secrets live in Evlio’s vault, never in an agent config or a partner machine. Rotate without redistributing anything.
03
Posture
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.
CONTROL
STATUS
NOTES
SOC 2 Type II
certified
Held by Evlio, covering the infrastructure Evlio runs on. Report under NDA.
ISO 27001 / 27701
certified
Information security and privacy management, held by Evlio. Certificates on request.
GDPR
compliant
DPA available, EU data residency on request
Encryption
TLS 1.3 / AES-256
In transit and at rest, per-tenant isolation
SSO / SAML and SCIM
available
Enterprise plans, your IdP owns publish rights
Penetration testing
annual
Third-party, summary shared under NDA
Vulnerability disclosure
open
hello@evlio.xyz, one business day response
Data residency
configurable
Regional hosting, private cloud, or on-prem
04
When 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 revocation
Keys, agents, and servers can be killed independently. In-flight calls are cut, not drained.
Anomaly alerts
Error-rate spikes, scope escalation attempts, and retry storms page you before a partner notices.
Forensics on demand
Filter the full log by agent, key, tool, or outcome, and export to your SIEM as JSON, CSV, or webhook.
Report something to
hello@evlio.xyz
. We respond within one business day and credit every valid finding.
FAQ
How does Evlio 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 Evlio 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@evlio.xyz. Reports get a response within one business day.
From top startups to Fortune 500 companies, trusting Evlio
SOC 2 Type II
·
certified
ISO 27001 / 27701
·
certified
GDPR
·
compliant
Encryption
·
TLS 1.3 / AES-256
SSO / SAML and SCIM
·
available
Full security posture →
RELATED READING
Governance
Aug 29
·
8
min
How teams actually control what AI agents can access
Read →
MCP
Aug 30
·
9
min
Tools to build governed MCP servers for agents, compared
Read →
Governance
Aug 27
·
4
min
An API governance checklist that fits in one pipeline
Read →
Send this page to your security team
They will ask about scopes, logs, residency, and revocation. All of it is answered here.
Request the security pack
See plans