How it works
The few ideas behind Leap360, in the order an agent meets them.
The path of one action
- Your agent asks to do something. A model returns a tool call, or your code calls a function you wrapped with
wrapTool, or a call goes through the MCP proxy. - Leap360 classifies it. In under a millisecond, in your process, it decides what kind of action this is (a shell command, a database drop, a deploy, a payment) and flags risky arguments such as credentials, personal data, production targets, or "everything at once".
- Your policies decide. Each policy can allow, warn, hold for approval or block.
- The project's mode applies the decision. In shadow mode nothing is blocked and the decision is only recorded. In enforce mode a block stops the call and a hold waits for a person.
- Everything is recorded. The call, its decision, its outcome and a redacted preview of the result go to your console and to Evidence.
Key terms
| Term | Meaning |
|---|---|
| Agent | Anything that acts with an API key: named by the serviceName or agentName you pass, or by --agent on the MCP proxy. |
| Action | One tool call: what the agent tried to do, with its arguments. |
| Policy | A rule about what agents may say or do, with an action: warn, hold for approval, or block. |
| Shadow mode | Policies run and record what they would do. Nothing is blocked. New projects start here for 7 days. |
| Enforce mode | Policies take effect. Blocked calls never run; held calls wait for a person. |
| Approval | A held call waiting for a person to approve or reject it. |
| Kill switch | Stops one agent, or the whole project, right away. |
| Evidence | The tamper-evident record of every decision, for audits and incident reviews. |
Who can loosen governance
An API key can always make governance stricter: stop agents, switch to enforce, add policies. Making it looser needs a person signed in to the console: restarting an agent, turning shadow mode on, deciding approvals, and changing or deleting policies. An agent therefore cannot approve its own request or lift its own kill switch.
What leaves your process
Classification and scanning run locally. Leap360 receives the action, its decision, and a redacted preview of the result: secrets, card numbers and emails are masked before anything is sent. See Security and data handling.