AI agents call getBlockWithdrawals to retrieve information from Agentek Eth without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
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.
Documented attack patterns abuse exactly the kind of access getBlockWithdrawals gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Agentek Eth, and nothing reaches the server without passing your rules. This is the rule we recommend for getBlockWithdrawals:
{
"version": "1",
"default": "deny",
"tools": {
"getBlockWithdrawals": {}
}
}getBlockWithdrawals is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
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.
Start from Agentek Eth, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
165 Agentek Eth tools catalogued and risk-classified — across an index of 43,000+ MCP servers.