get_base_storage
Read one storage slot on Base via eth_getStorageAt.
This record as markdown: /tools/io-github-davidmosiah-delx-protocol/get-base-storage.md
What get_base_storage does on Delx Protocol — Agent Recovery & Continuity
AI agents call get_base_storage 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 |
|---|---|---|---|
slot | string | integer | Yes | |
block | string | — | |
address | string | Yes |
Parameters from the server's own tool schema.
Why get_base_storage is rated Low
This tool queries blockchain storage state without modifying, executing code, or triggering external operations. It is a straightforward read operation against the Base blockchain. The blast radius of misuse is minimal—an AI agent could at worst enumerate or exfiltrate public blockchain data already visible on-chain. No reversible writes, destructive actions, or financial operations are possible.
From the tool's definition Tool name is 'get_base_storage' and description states 'Read one storage slot on Base via eth_getStorageAt'. The verb 'Read' and the use of eth_getStorageAt (a read-only RPC method) confirm this is a data retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs get_base_storage 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_storage, this is the rule to start with:
get_base_storage 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_storage call is checked against it from then on.
Questions about get_base_storage
Read one storage slot on Base via eth_getStorageAt. 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_storage accepts 3 parameters: slot, block, address. Required: slot, 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_base_storage: 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_storage 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_storage 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_storage. 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_storage 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