Arbiter
com.arbiterscan/arbiter
Security checks for apps built with AI: leaked keys, open routes, database rules, each with a fix.
Install surfaces
How Arbiter runs, per the official MCP registry entry.
- streamable-http
https://api.arbiterscan.com/mcp
Governed execution
How KLA gates calls to Arbiter once it is connected.
A published policy defines which Arbiter actions an agent may take and under what conditions. Each call passes through a policy gate at the tool-call boundary. Permitted actions execute, with the policy basis recorded. Flagged actions execute and are sampled for scheduled human review. High-stakes actions pause and route to a named reviewer on the Decision Desk. The call, the policy decision, and any approval are sealed as an evidence record.
KLA also governs the agents and model providers you already run. See integrations.