Get detailed information about an address including native coin balance (formatted in ETH with USD value), token count, transaction count, and whether it is a contract.
AI agents call getAddressInfo 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 only retrieves and queries blockchain data about an Ethereum address. It performs no state changes, executes no code, moves no funds, and produces no side effects. It is a simple read-only information lookup, analogous to a blockchain explorer query.
From the tool's definition Tool description states it 'Get[s] detailed information about an address' including balances, counts, and contract status. Keywords: 'Get', 'information', 'balance', 'count' all indicate pure retrieval with no modification or execution of code.
Documented attack patterns abuse exactly the kind of access getAddressInfo 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 getAddressInfo:
{
"version": "1",
"default": "deny",
"tools": {
"getAddressInfo": {}
}
}getAddressInfo 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 detailed information about an address including native coin balance (formatted in ETH with USD value), token count, transaction count, and whether it is a contract. 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 getAddressInfo: 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.
getAddressInfo 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 getAddressInfo 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 getAddressInfo. 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.
getAddressInfo 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.