getBlockTransactions

Get transactions within a specific block

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/getblocktransactions.md

WHAT IT DOES

What getBlockTransactions does on Agentek Eth

AI agents call getBlockTransactions 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 getBlockTransactions is rated Low

This tool retrieves historical blockchain transaction data from a specific block. It performs a read-only query operation against the Ethereum blockchain, similar to a database SELECT statement. There is no indication of data modification, deletion, code execution, or financial transactions.

From the tool's definition Tool name 'getBlockTransactions' and description 'Get transactions within a specific block' indicate a data retrieval operation. The verb 'Get' combined with 'transactions' denotes querying blockchain data with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs getBlockTransactions 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 getBlockTransactions, this is the rule to start with:

getBlockTransactions Allowed

getBlockTransactions 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": {
    "getBlockTransactions": {}
  }
}

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 getBlockTransactions call is checked against it from then on.

FAQ

Questions about getBlockTransactions

What does the getBlockTransactions tool do? +

Get transactions 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.

How do I enforce a policy on getBlockTransactions? +

Register the Agentek Eth MCP server in PolicyLayer and add a rule for getBlockTransactions: 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 getBlockTransactions? +

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

Can I rate-limit getBlockTransactions? +

Yes. Add a rate_limit block to the getBlockTransactions 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 getBlockTransactions completely? +

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

getBlockTransactions 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 →