Tower (AI protection) · Agent Firewall

Every tool call your AI agents make, checked and on the record.

Every tool call your agents make, checked and on record. Agents act on their own, at machine speed. Raidu puts every message and every tool call through the same policy stack, and scans what the tool sends back before the agent reads it.

Runs inside your AWS, GCP or Kubernetes install.

Last reviewed

Illustrative. No customer data.

The difference

Their way, and ours.

Their wayRaidu
Govern the prompt, trust the tools.Govern the prompt and every tool call.
Tool output flows straight into the agent.Tool output is scanned for personal data before the agent sees it.
An agent's run is a black box.Every step of the run is on the record, in order.

473 prebuilt tools across 33 categories, each call checked on the way out and scanned on the way back.

Source: Tower agent catalog and tool executor

The record

The tool call, on the record.

Every step an agent takes and every tool it calls becomes a tamper-evident audit record, in order.

Record 7,291 Agent step · 15:17:44Z
Agent
sales-assistant · step 7 of 12
Tool
slack-send-message
Call verdict
Allowed
Output scan
2 entities masked
Proof
Tamper-evident, on record
sha256 2905b86a12dd47b5ec93d82cb69c975f…
entry 7,291 of 16,842 · write-once

The call path

Where Raidu acts.

  1. InterceptEvery agent message and tool call
  2. ResolveWhich agent, which tool, which data
  3. InspectTool call and tool output
  4. DecideBlock or allow
  5. ProveTamper-evident record for each step

Also covered

  • Tool catalog
  • Output scanning
  • Step records
  • Agent policies
  • Tool binding

Common questions

Answered straight.

Which tools are available?
473 prebuilt tool templates across 33 categories, plus your own.
Is the tool output checked?
Yes, for personal data, before it reaches the agent.
Can I see what an agent did at a given step?
Yes. Every step of the call chain is written to the tamper-evident record in order.
Can we restrict which tools an agent can call?
Yes. Policy sets are configured per agent and per organisation. A call that does not match the allowed set is blocked and the decision is logged.

Let agents act. Keep the record.