get_delx_claim_proof
Return a Merkle claim proof for a wallet and epoch when DELX rewards are claimable. Free
This record as markdown: /tools/io-github-davidmosiah-delx-protocol/get-delx-claim-proof.md
What get_delx_claim_proof does on Delx Protocol — Agent Recovery & Continuity
AI agents call get_delx_claim_proof to retrieve information from Delx Protocol — Agent Recovery & Continuity without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
epoch | integer | Yes | Reward epoch number |
wallet_address | string | Yes | Bound wallet address; ERC20 DELX claims require a Base/EVM wallet |
Parameters from the server's own tool schema.
Why get_delx_claim_proof is rated Low
This tool retrieves and returns a Merkle proof—a cryptographic attestation of eligibility. It queries state to determine claimability but does not modify data, execute external operations, or move funds. The proof itself is read-only verification data.
From the tool's definition Tool name 'get_delx_claim_proof' and description 'Return a Merkle claim proof for a wallet and epoch when DELX rewards are claimable' indicate data retrieval without side effects. Returns cryptographic proof data in a read-only manner.
Attacks that exploit this kind of access
The rule that runs get_delx_claim_proof safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx Protocol — Agent Recovery & Continuity, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_delx_claim_proof, this is the rule to start with:
get_delx_claim_proof is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Delx Protocol — Agent Recovery & Continuity, apply this rule, and every get_delx_claim_proof call is checked against it from then on.
Questions about get_delx_claim_proof
Return a Merkle claim proof for a wallet and epoch when DELX rewards are claimable. Free. It is categorised as a Read tool in the Delx Protocol — Agent Recovery & Continuity MCP Server, which means it retrieves data without modifying state.
get_delx_claim_proof accepts 2 parameters: epoch, wallet_address. Required: epoch, wallet_address. The full parameter table on this page comes from the server's own tool schema.
Register the Delx Protocol — Agent Recovery & Continuity MCP server in PolicyLayer and add a rule for get_delx_claim_proof: 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 Delx Protocol — Agent Recovery & Continuity. Nothing to install.
get_delx_claim_proof is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_delx_claim_proof 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.
Set action: deny in the PolicyLayer policy for get_delx_claim_proof. 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.
get_delx_claim_proof is provided by the Delx Protocol — Agent Recovery & Continuity MCP server (https://api.delx.ai/v1/mcp?src=registry). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx Protocol — Agent Recovery & Continuity, and thousands of servers like it.
Across the catalogue