Low Risk

ponzu_farm_claim

Claim primary token rewards from a Ponzu farm. One-time claim per LiquidityCard. After claiming, no further token or ETH claims are possible for this card.

Part of the Ponzu App server.

ponzu_farm_claim is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE PONZU APP →

Free to start. No card required.

AI agents call ponzu_farm_claim to retrieve information from Ponzu App without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though ponzu_farm_claim only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "ponzu_farm_claim": {}
  }
}

See the full Ponzu App policy for all 16 tools.

Get this rule live on your own Ponzu App server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY PONZU APP →

View all 16 tools →

These attack patterns abuse exactly the kind of access ponzu_farm_claim gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so ponzu_farm_claim only ever does what you allow.

SECURE PONZU APP →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the ponzu_farm_claim tool do? +

Claim primary token rewards from a Ponzu farm. One-time claim per LiquidityCard. After claiming, no further token or ETH claims are possible for this card.. It is categorised as a Read tool in the Ponzu App MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on ponzu_farm_claim? +

Register the Ponzu App MCP server in PolicyLayer and add a rule for ponzu_farm_claim: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Ponzu App. Nothing to install.

What risk level is ponzu_farm_claim? +

ponzu_farm_claim is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit ponzu_farm_claim? +

Yes. Add a rate_limit block to the ponzu_farm_claim rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block ponzu_farm_claim completely? +

Set action: deny in the PolicyLayer policy for ponzu_farm_claim. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides ponzu_farm_claim? +

ponzu_farm_claim is provided by the Ponzu App MCP server (PonzuTech/ponzu_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Ponzu App tool call.

Deterministic rules across all 16 Ponzu App 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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.