get_base_call
Bounded read-only eth_call on Base (max 4KB).
This record as markdown: /tools/io-github-davidmosiah-delx-protocol/get-base-call.md
What get_base_call does on Delx Protocol — Agent Recovery & Continuity
AI agents call get_base_call 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 |
|---|---|---|---|
to | string | Yes | |
data | string | — | |
from | string | — | |
block | string | — |
Parameters from the server's own tool schema.
Why get_base_call is rated Low
This tool performs a constrained query operation on the Base blockchain. It retrieves data without side effects, aligns with the 'Read' category definition (retrieves data; no side effects), and the low severity reflects minimal blast radius—a misused read-only call cannot alter state, execute arbitrary code, or cause financial harm. The bounded 4KB limit further constrains risk.
From the tool's definition Tool description explicitly states 'Bounded read-only eth_call' with a size limit of 4KB. The term 'read-only' clearly indicates no data modification, creation, or deletion occurs.
Attacks that exploit this kind of access
The rule that runs get_base_call 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_call, this is the rule to start with:
get_base_call 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_call call is checked against it from then on.
Questions about get_base_call
Bounded read-only eth_call on Base (max 4KB). 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_call accepts 4 parameters: to, data, from, block. Required: to. 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_call: 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_call 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_call 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_call. 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_call 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