AI Firewall
Tax IDs, cards and secrets handled before they reach the model
AI Firewall is the workspace policy applied to every AI call that goes through the platform: chat, agents, flows and the API. Before the call reaches the model, the Gateway looks for sensitive data in the text, and each category can be blocked, masked or allowed. The model response goes through the same policy, including when streaming.
The same policy holds usage limits: budget per key, requests per minute and concurrent calls per workspace, and blocked tools. For MCP tools, each call's arguments are checked against the declared schema; outside the schema, the call is refused.
How it works
- Recognized categories: CPF, CNPJ (Brazilian tax IDs), card, bank account, Pix key, boleto and secrets (tokens, passwords, keys), blocked by default; email and phone, allowed by default.
- In mask mode, the value is replaced with a placeholder such as [CPF_1], and the original never comes back in the response.
- Per-workspace limit on requests per minute and concurrent calls (60 per minute and 20 concurrent by default).
- A tool blocked by the policy is refused even after it has been approved in an agent.
- The organization can set a ceiling above its workspaces: allowed models and providers, minimum masking and blocked tools. A workspace can only restrict further.
- Every decision goes into the hash-chained audit log, exportable as JSON and CSV and verifiable outside the platform.
Input blocked at the Gateway: 422 sensitive_data_blocked
Output blocked: 422 sensitive_output_blocked
Over the limit: 429 rate_limited or 429 concurrency_limitedWhat it does not do
- It only applies to traffic that goes through the platform, the browser extension or the perimeter proxy.
- Names, addresses and health data are not recognized.
- The requests-per-minute limit applies per workspace, not per key.
- It is not a certification: AIUBY holds no third-party security certification.