Blazle – Block prompt injection and secret leaks before AI agents act

Blazle launched an in-flight security layer that sits between AI agents and the model, shell or repository, inspecting every prompt, shell command and code diff before it leaves the environment. Blazle says its BLAZIL engine performs static detection in roughly 0.2 ms per request and runs an AI prompt-injection check in 50-100 ms only when needed, catching attacks in more than 30 languages, with figures measured in production in October 2026. The product ships as an IDE edge proxy for VS Code, Cursor, Claude Code and Antigravity, a REST API with sub-250 ms guardrails, MCP and voice-agent coverage, and a GitHub App that scans pull requests before merge, and Blazle states it makes zero third-party AI calls for detection so payloads never leave its environment.

In-flight security for AI agents Security that runs in flight. BLAZLE sits between your AI agents and the world. Every prompt, shell command and code diff is inspected before it leaves your environment: secrets redacted, injections blocked in 30+ languages, risky actions held for a human. 40-second tour: redact, block, approve, audit. ~0.2 ms Static detection per request under 2 ms 50-100 ms AI prompt-injection check only when it is needed 30+ Languages attacks are caught in tested: EN · VI · ZH · ID · TH · JA 0 Third-party AI calls for detection your payload never leaves BLAZLE Measured in production, October 2026. Methodology https://www.blazle.io/benchmarks 03 / Approach Interception, not detection. Most tools look at what already happened. BLAZLE decides at the moment a payload is produced, before anything leaves. After the fact - Scans logs or commits after the payload has already left - Exposed secrets get rotated and hoped for - Alerts arrive minutes or hours later - Nothing stops the request at the moment of egress In flight, with BLAZLE - Evaluated the instant it is produced, before it goes anywhere - Blocked before it reaches the model, the shell or the repository - Static rules in ~0.2 ms, ML injection check in 50-100 ms - Attacks caught in 30+ languages, not just English - Per-tenant policy: block, redact or log - Detected secrets are masked before anything is stored AI agent VS Code · Cursor · Claude Code · Antigravity · Auralius Voice · your pipeline BLAZLE · BLAZIL engine scan · score · decide · ~0.2 ms Model · shell · repo only what passed policy 04 / Platform One interceptor. Four ways in. The same detection engine, policy and audit trail, wherever your agents work. 01 https://www.blazle.io/docs/proxy-cli IDE & Vibe Coding Set-and-forget edge proxy for VS Code, Cursor, Claude Code, Antigravity — 1-second install, silent background daemon. Docs 02 https://www.blazle.io/docs/api-prompt REST & In-Flight Tools Sub-250ms guardrails for prompts, shell commands, code diffs, and structured tool calls. Docs 03 https://www.blazle.io/docs/mcp-copilot MCP & Voice Agents Zero-latency security for Auralius voice pipelines and MCP tools with human-in-the-loop approvals. Docs 04 https://www.blazle.io/docs/github-app GitHub App Pull requests are scanned before merge. Blocked findings request changes on the PR. Docs Multilingual by default Any language. Every surface. Attackers do not only write in English. BLAZLE catches attempts to hijack your AI in more than 30 languages, including encoded and hidden-character tricks, and lets through messages that only talk about attacks. - REST API & Playground Prompts and outputs in any of 30+ languages, checked the same way. - MCP Copilot Every chat message and tool call, whatever language it is written in. - IDE proxy Prompts from your coding tools get the same multilingual AI check. - GitHub App Planted instructions in the files your coding agents follow, in any language. - Policy Library Write policies in one language, ask and enforce them in another. 05 / Your policies Your rules, in plain language. BLAZLE reads the security policies your company already wrote. No regex, no rule syntax, and your documents never leave BLAZLE. 1. 01 Add your policiesUpload the security policies you already have: PDF, Word, Markdown or plain text. 2. 02 Ask them anythingAsk in your own words and language. A policy written in Vietnamese answers a question asked in English, and the other way round. 3. 03 Turn a section into a ruleGive two or three examples. BLAZLE flags messages that mean the same, then blocks once you are ready. When something is blocked, see which of your policies it relates to, in one click. How the Policy Library works https://www.blazle.io/docs/policy-library 06 / Agent Sweep No agent without an owner. Teams create agents in minutes and rarely clean them up. Agent Sweep finds every API key and MCP token that acts for your team and shows which ones nobody looks after any more. 1. 01 See every agentOwner, last use, expiry and rights of every key and token, plus agent files and MCP configurations found in your repositories. 2. 02 Catch the orphansOwner left, committed to a repository, write rights it never uses, unused for weeks. An MCP token stops working the moment its owner leaves. 3. 03 Contain, then revokeQuarantine in one click and restore just as fast. Revocation goes through approval and needs a second person. Seeing every agent is free on every plan. Pro and Business include 50 and 250, then $2 per agent per month. How Agent Sweep works https://www.blazle.io/docs/agent-sweep Running your own MCP servers? MCP Gateway puts BLAZLE in front of them: approve, block or switch off any tool an agent can call. How MCP Gateway works https://www.blazle.io/docs/mcp-gateway 07 / Get started Set up in under three minutes. From a free account to protected agents, step by step: API key, first intercept, rules, your machine, GitHub, the MCP Copilot and audit. 08 / Dogfooding We secure BLAZLE with BLAZLE. Every pull request to BLAZLE, and to every repository across our parent company Kolerr Lab, is scanned by the BLAZLE GitHub App before merge. Our own AI Copilot, a full MCP server that can manage rules, incidents, API keys and policies, gets no special treatment either: everything it does runs through the same interceptor our customers rely on. 1. 01 Prompt scannedEvery message to the Copilot's AI model is inspected by BLAZLE before it leaves. 2. 02 Role checkedEach tool call needs the caller's own permission. No backdoor for the assistant. 3. 03 Action interceptedIf BLAZLE would block it for a customer, it blocks its own Copilot too. 4. 04 Human approvalChanges wait for a person. Destructive ones need a second approver. 5. 05 AuditedProposal, decision and execution land in the tamper-evident audit log. If we wouldn't trust it with our own platform, we wouldn't ask you to. How the MCP Copilot works https://www.blazle.io/docs/mcp-copilot 09 / Built for Developers ship. Security sleeps. One line in front of every model call. - REST API for prompts, shell commands and code diffs - Local IDE proxy, VS Code extension and git pre-commit hook - Clear verdict on every call: allowed, risk rating, matched rule Read the quickstart https://www.blazle.io/docs/quickstart curl -X POST https://api.blazle.io/api/v1/intercept/prompt \ -H "X-API-Key: blz live ..." \ -H "Content-Type: application/json" \ -d '{"prompt": "Deploy using this key: AKIA..."}' { "allowed": false, "risk rating": "Critical", "findings": { "rule name": "AWS Access Key" } } 10 /Design partners Shipping agents to production? Build it with us. We work closely with a small group of teams running AI agents in real environments. Partners get direct access to the engineers, a say in the roadmap and hands-on help with rollout. Apply as a design partner https://www.blazle.io/contact?topic=design-partner Questions, answered Does BLAZLE add latency to my agent? Measured in production October 2026 : static detection takes ~0.2 ms per request under 2 ms . The AI prompt-injection check adds 50-100 ms, and only runs when it is needed. Do you store my prompts or secrets? Allowed requests are not stored. When a request is blocked we keep an investigation record with detected secrets masked, for your plan's retention period. The secret itself is never persisted, and detection never sends your payload to a third-party AI service. How is this different from a secret scanner? Scanners run after the fact, on logs or commits, once the secret has already left. BLAZLE sits in the path and decides before the payload reaches the model, the shell or the repository. Which agents does it work with? Anything that sends prompts, runs commands or writes code: Cursor, Copilot, Devin, custom pipelines over REST, and pull requests through the GitHub App. Does BLAZLE work in languages other than English? Yes. Attempts to hijack an AI are caught in more than 30 languages, and we test English, Vietnamese, Chinese, Indonesian, Thai and Japanese ourselves, including encoded and hidden-character tricks. Messages that only talk about attacks are not blocked. This works on every surface: the API, the MCP Copilot, the IDE proxy and the GitHub App. The Policy Library is multilingual too: a policy written in one language answers questions asked in another. Can BLAZLE follow our own security policies? Yes. Upload the policies you already have to the Policy Library, ask them questions in plain language, and turn any section into a rule from a few example messages. New rules warn first and block once you switch them on. Your documents stay inside BLAZLE. How does BLAZLE help with compliance? Findings are scored on a MAS-TRM Likelihood × Impact matrix, and BLAZLE ships the evidence an auditor asks for: a tamper-evident audit chain, retention posture, access review and exportable evidence bundles for MAS-TRM and SOC 2 audits. 11 /Start Your agents are already running. Make them run safely. Free forever on the Hacker tier: 5,000 intercepted requests a month. No credit card required. Watch the 3-minute setup setup Powered by the BLAZIL engine · 234K TPS fintech-grade core