get_base_block_by_hash
Return a Base block header by hash.
This record as markdown: /tools/io-github-davidmosiah-delx-protocol/get-base-block-by-hash.md
What get_base_block_by_hash does on Delx Protocol — Agent Recovery & Continuity
AI agents call get_base_block_by_hash 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 |
|---|---|---|---|
full | boolean | — | |
block_hash | string | Yes |
Parameters from the server's own tool schema.
Why get_base_block_by_hash is rated Low
This tool queries blockchain data (a Base block header) by its hash parameter and returns it. The operation is read-only with no side effects, does not execute code, does not modify data, and does not involve financial transactions. It is a straightforward data retrieval operation typical of blockchain inspection tools.
From the tool's definition Tool name 'get_base_block_by_hash' and description 'Return a Base block header by hash' indicate a retrieval operation with no modification or execution of external operations.
Attacks that exploit this kind of access
The rule that runs get_base_block_by_hash 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_block_by_hash, this is the rule to start with:
get_base_block_by_hash 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_block_by_hash call is checked against it from then on.
Questions about get_base_block_by_hash
Return a Base block header by hash. 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_block_by_hash accepts 2 parameters: full, block_hash. Required: block_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_block_by_hash: 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_block_by_hash 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_block_by_hash 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_block_by_hash. 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_block_by_hash 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