This record as markdown: /tools/nanidao-agentek/getblockwithdrawals.md
What getBlockWithdrawals does on Agentek Eth
AI agents call getBlockWithdrawals 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.
Why getBlockWithdrawals is rated Low
This tool queries blockchain data to retrieve withdrawal information from a specified block. It performs passive data retrieval without modifying state, executing code, or moving funds. The most severe risk would be information disclosure, which is minimal for publicly accessible blockchain data. No write, execute, destructive, or financial operations are performed.
From the tool's definition Tool name 'getBlockWithdrawals' and description 'Get withdrawals within a specific block' indicate a query/retrieval operation. The verb 'Get' and the context of retrieving blockchain data shows this is a read-only operation with no side effects.
Attacks that exploit this kind of access
The rule that runs getBlockWithdrawals 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 getBlockWithdrawals, this is the rule to start with:
getBlockWithdrawals 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 Agentek Eth, apply this rule, and every getBlockWithdrawals call is checked against it from then on.
Questions about getBlockWithdrawals
Get withdrawals within a specific block. It is categorised as a Read tool in the Agentek Eth MCP Server, which means it retrieves data without modifying state.
Register the Agentek Eth MCP server in PolicyLayer and add a rule for getBlockWithdrawals: 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.
getBlockWithdrawals 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 getBlockWithdrawals 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 getBlockWithdrawals. 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.
getBlockWithdrawals 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.
More on Agentek Eth, and thousands of servers like it.
This server
Across the catalogue