getAddressWithdrawals

Get beacon chain withdrawals received by a specific address.

SERVERAgentek Eth SOURCEnanidao/agentek

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/nanidao-agentek/getaddresswithdrawals.md

WHAT IT DOES

What getAddressWithdrawals does on Agentek Eth

AI agents call getAddressWithdrawals to retrieve information from Agentek Eth without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why getAddressWithdrawals is rated Low

This tool retrieves blockchain withdrawal data for a specified address. It performs a query against the beacon chain without modifying, executing, or destroying any data. The action is informational and has no irreversible consequences, placing it squarely in the Read category with low severity.

From the tool's definition Tool name 'getAddressWithdrawals' and description 'Get beacon chain withdrawals received by a specific address' indicate a query/retrieval operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs getAddressWithdrawals safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Agentek Eth, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getAddressWithdrawals, this is the rule to start with:

getAddressWithdrawals Allowed

getAddressWithdrawals is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "getAddressWithdrawals": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Agentek Eth, apply this rule, and every getAddressWithdrawals call is checked against it from then on.

FAQ

Questions about getAddressWithdrawals

What does the getAddressWithdrawals tool do? +

Get beacon chain withdrawals received by a specific address. It is categorised as a Read tool in the Agentek Eth MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getAddressWithdrawals? +

Register the Agentek Eth MCP server in PolicyLayer and add a rule for getAddressWithdrawals: 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 Agentek Eth. Nothing to install.

What risk level is getAddressWithdrawals? +

getAddressWithdrawals is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit getAddressWithdrawals? +

Yes. Add a rate_limit block to the getAddressWithdrawals 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.

How do I block getAddressWithdrawals completely? +

Set action: deny in the PolicyLayer policy for getAddressWithdrawals. 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.

What MCP server provides getAddressWithdrawals? +

getAddressWithdrawals is provided by the Agentek Eth MCP server (nanidao/agentek). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Agentek Eth, and thousands of servers like it.

This server

All 193 Agentek Eth tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →