
Pre-Inference MCP & Agent Firewall
Inspects every Model Context Protocol (MCP) tool invocation, enforcing per-environment allowlists and blocking indirect prompt-injection payloads before execution.
Register every AI agent and MCP tool, enforce allowlists, block prompt injection and redact secrets before a model ever sees them.

Inventory every agent, model, owner and MCP server in one place.
Define exactly which tools each agent may call, per environment.
Detect indirect injection in user input and retrieved content.
API keys, tokens and personal data are removed before inference.
Writes, payments and shell commands are routed for step-up approval.
Every allow, block and approval is recorded with its rationale.

Inspects every Model Context Protocol (MCP) tool invocation, enforcing per-environment allowlists and blocking indirect prompt-injection payloads before execution.

Automatically redacts bearer tokens, API keys and personal data before model inference and writes every allow/block decision to an append-only ledger.
CSH-RULE-001..004) mapped to MITRE ATT&CK (T1110.001, T1098.003, T1048, T1190) with idempotent dedupe_key ingestion and SHA-256 immutable event hashes.[REDACTED_SECRET], [REDACTED_PII]), explicit per-agent Model Context Protocol (MCP) tool allowlists, and indirect prompt-injection blocking.ENABLE / FORCE ROW LEVEL SECURITY across all 20 tenant tables bound to transaction-local current_tenant_id(); cross-tenant queries fail closed with HTTP 403.isolate_host) and credential revocation require named human step-up approval recorded in an append-only audit trail.DNS TXT or HTTP ownership token required before scanning. Continuous evidence aligned with UK NCSC Cyber Essentials Plus, UK GDPR & Data Protection Act 2018, ISO/IEC 27001:2022.ML-KEM / ML-DSA), and 2035 full PQC completion.FORCE ROW LEVEL SECURITY on all 20 tenant tables.ALTER TABLE security_events ENABLE ROW LEVEL SECURITY; ALTER TABLE security_events FORCE ROW LEVEL SECURITY; CREATE POLICY tenant_isolation_policy ON security_events FOR ALL TO csh_app_role USING (organization_id = current_tenant_id()) WITH CHECK (organization_id = current_tenant_id());
No. Detection is driven by deterministic rules. ARYA SAI only produces advisory summaries from redacted evidence, and every containment action requires a named human approver.
You choose UK (London) or EU (Frankfurt) residency at onboarding. Additional regions are available on Enterprise plans.
CSH Compliance helps you prepare evidence for these schemes. We do not claim certifications we have not been awarded; our own certification status is published on the Trust page.
Only assets you have verified ownership of via DNS or HTTP token. Unverified assets cannot be scanned or ingested.
Yes. The partner edition supports delegated tenants, pooled licensing and partner billing.

A 30-minute scoped walkthrough with a security engineer. No slides.