16 tools. 4 can modify or destroy data without limits.
1 destructive tool with no built-in limits. Policy required.
Last updated:
Financial operations (ponzu_presale_refund) can move real money. An agent caught in a loop could drain accounts before anyone notices.
Execute tools (ponzu_calc_pricing, ponzu_deploy, ponzu_trigger_launch) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.
Intercept sits between your agent and Ponzu App. Every tool call checked against your policy before it executes — so your agent can do its job without breaking things.
npx -y @policylayer/intercept scan -- npx -y @ponzu_app/mcp ponzu_presale_refund:
rules:
- action: deny Financial tools should be explicitly enabled per use case, not open by default.
ponzu_claim_eth:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
Yes. The Ponzu App server exposes 1 financial tools including ponzu_presale_refund. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. Intercept lets you block financial tools by default or set per-tool rate limits.
16 tools across 3 categories: Execute, Financial, Read. 12 are read-only. 4 can modify, create, or delete data.
One line change. Instead of running the Ponzu App server directly, prefix it with Intercept: intercept -c io-github-ponzutech-ponzu.yaml -- npx -y @@ponzu_app/mcp. Download a pre-built policy from policylayer.com/policies/io-github-ponzutech-ponzu and adjust the limits to match your use case.
Starter policies available for each. Same risk classification, same one-command setup.
Set budgets, approvals, and hard limits across MCP servers.
npx -y @policylayer/intercept init