prepare_delx_claim_transaction
Return an agent-executable Base transaction for a published DELX Merkle claim. Set simulate=true for a read-only eth_call preflight. The agent signs locally; Delx never receives private keys. Free
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-a2a/prepare-delx-claim-transaction.md
What prepare_delx_claim_transaction does on Delx Mcp A2a
AI agents use prepare_delx_claim_transaction to create or update resources in Delx Mcp A2a, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Delx Mcp A2a environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
epoch | integer | Yes | Published reward epoch number |
simulate | boolean | — | Run eth_call + eth_estimateGas without signing or broadcasting |
wallet_address | string | Yes | Bound Base/EVM wallet that will sign and pay gas |
Parameters from the server's own tool schema.
Why prepare_delx_claim_transaction is rated Medium
An AI agent can call prepare_delx_claim_transaction faster than any human can review: one bad instruction and it creates or modifies resources in Delx Mcp A2a by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs prepare_delx_claim_transaction safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx Mcp A2a, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For prepare_delx_claim_transaction, this is the rule to start with:
prepare_delx_claim_transaction stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Delx Mcp A2a, apply this rule, and every prepare_delx_claim_transaction call is checked against it from then on.
Questions about prepare_delx_claim_transaction
Return an agent-executable Base transaction for a published DELX Merkle claim. Set simulate=true for a read-only eth_call preflight. The agent signs locally; Delx never receives private keys. Free. It is categorised as a Write tool in the Delx Mcp A2a MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
prepare_delx_claim_transaction accepts 3 parameters: epoch, simulate, wallet_address. Required: epoch, wallet_address. The full parameter table on this page comes from the server's own tool schema.
Register the Delx Mcp A2a MCP server in PolicyLayer and add a rule for prepare_delx_claim_transaction: 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 Mcp A2a. Nothing to install.
prepare_delx_claim_transaction is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the prepare_delx_claim_transaction 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 prepare_delx_claim_transaction. 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.
prepare_delx_claim_transaction is provided by the Delx Mcp A2a MCP server (https://api.delx.ai/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx Mcp A2a, and thousands of servers like it.
This server
Across the catalogue