1060 tools. 455 can modify or destroy data without limits.
46 destructive tools with no built-in limits. Policy required.
Last updated:
Verified server · catalogue entry verified 29/06/2026 · full schemas captured for 837 of 1060 tools
Running more than one server? Check your whole stack →
Full per-tool breakdown → Model it in the token calculator →
455 of Yaver's 1060 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.
PolicyLayer is an MCP gateway — it sits between your AI agents and Yaver, and nothing reaches the server without passing your rules. These are the rules we recommend:
{
"session_transfer": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
} Financial tools should be explicitly enabled per use case, not open by default.
{
"acl_remove_peer": {
"deny_if": [
{
"conditions": [],
"on_deny": "Blocked by default. Requires approval."
}
]
}
} Destructive tools should never be available to autonomous agents without human approval.
{
"ab_assign": {
"limits": [
{
"counter": "ab_assign_per_hour",
"window": "hour",
"max": 30,
"scope": "grant"
}
]
}
} Prevents bulk unintended modifications from agents caught in loops.
{
"ab_event": {
"limits": [
{
"counter": "ab_event_per_minute",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
} Controls API costs and prevents retry loops from exhausting upstream rate limits.
Instant setup, no code required.
Other MCP servers with similar tools — same risk classification, starter policies for each.
Yes. The Yaver server exposes 1 financial tools including session_transfer. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. PolicyLayer lets you block financial tools by default, require human approval, or set per-tool rate limits — enforced on every call.
Yes. The Yaver server exposes 45 destructive tools including acl_remove_peer, cancel_schedule, cargo_remove_crate. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.
The Yaver server has 214 write tools including ab_assign, ab_experiment_create, account_connect. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Yaver.
1060 tools across 5 categories: Destructive, Execute, Financial, Read, Write. 605 are read-only. 455 can modify, create, or delete data.
Register the Yaver MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.
Deterministic rules across all 1060 Yaver tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Instant setup, no code required.
1060 Yaver tools catalogued and risk-classified — across an index of 43,000+ MCP servers.