9 tools. 4 can modify or destroy data without limits.
3 destructive tools with no built-in limits. Policy required.
Last updated:
Free to start. No card required.
Full per-tool breakdown → Model it in the token calculator →
Financial operations (deposit, simulate_deposit, withdraw) can move real money. An agent caught in a loop could drain accounts before anyone notices.
Execute tools (claim_forge) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.
{
"deposit": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
} Financial tools should be explicitly enabled per use case, not open by default.
{
"get_balance": {
"limits": [
{
"counter": "get_balance_per_minute",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
} Controls API costs and prevents retry loops from exhausting upstream rate limits.
Yes. The Forge Treasury server exposes 3 financial tools including deposit, simulate_deposit, withdraw. 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.
9 tools across 3 categories: Execute, Financial, Read. 5 are read-only. 4 can modify, create, or delete data.
Register the Forge Treasury 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.
Starter policies for each. Same risk classification, live on your fleet in minutes.
Deterministic rules across all 9 Forge Treasury tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.