Laya Guard
Check every agent tool call before it runs
Check an agent’s tool call before it runs: allow, ask or block. Send the proposed call and what the user asked for; get a verdict with the reasons and nine calibrated scores in one pass. On your Laya Studio key, at $0.20 per 1k checks.
Laya Guard in numbers
- ~15 ms
- per check on an RTX 4090 (p95 ~23 ms)
- 9
- calibrated scores per check, one pass
- 0.855
- AUROC on the R-Judge test half
- $0.20
- per 1,000 checks
How it fits
One call in your pre-tool-call hook
The agent proposes a tool call, your hook sends it to the guard, and only an allow runs without a human. Ask goes to the user; block never runs.
- Agent frameworks. call POST /v1/guard from the hook that runs before every tool call.
- MCP clients and gateways. use the guard_check and guard_batch tools on https://api.laya.studio/mcp, with the same key.
- Code-mode sandboxes. check every call a generated script makes in one guard_batch request.
check.shbash
What it answers
Nine questions about every call, in one pass
| safe | Probability the call is safe to run now. |
|---|---|
| violation | none, policy_violation, scope_violation, injection, goal_drift or corrigibility. |
| severity | none < low < medium < high. |
| destructive | Deletes, overwrites or irreversibly changes data. |
| exfiltration | Sends private data, secrets or another tenant’s data where it should not go. |
| injected | Driven by instructions from a tool result or document, not the user (prompt injection). |
| approval_policy | auto_approve, require_human or reject. |
| blast_radius | read-only < local or reversible write < production-mutating or external side effect. |
| args_grounded | The arguments are supported by what the user asked (no invented ids, amounts or recipients). |
FAQ
Laya Guard, answered
Laya Guard
Guard your first agent today
One key, one balance for Laya Decisions and Laya Guard. $0.20 per 1k checks; failed checks are free.