get_base_transaction
Look up a Base transaction by hash with optional receipt.
This record as markdown: /tools/io-github-davidmosiah-delx-protocol/get-base-transaction.md
What get_base_transaction does on Delx Protocol — Agent Recovery & Continuity
AI agents call get_base_transaction 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 |
|---|---|---|---|
tx_hash | string | Yes | |
include_receipt | boolean | — |
Parameters from the server's own tool schema.
Why get_base_transaction is rated Low
This tool retrieves transaction data from the Base blockchain by hash and optionally returns receipt information. It performs a lookup/query with no ability to modify, execute code, or trigger financial transfers. The 'get_' prefix and 'look up' verb confirm read-only semantics.
From the tool's definition Tool name contains 'get_' and description states 'Look up a Base transaction' — a read-only query operation with no side effects.
Attacks that exploit this kind of access
The rule that runs get_base_transaction 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_base_transaction, this is the rule to start with:
get_base_transaction 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_base_transaction call is checked against it from then on.
Questions about get_base_transaction
Look up a Base transaction by hash with optional receipt. 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_base_transaction accepts 2 parameters: tx_hash, include_receipt. Required: tx_hash. 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_base_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 Protocol — Agent Recovery & Continuity. Nothing to install.
get_base_transaction 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_base_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 get_base_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.
get_base_transaction 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