New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

getHolders

Fetch the list of holders for a given ZAMM coin, ordered by balance descending.

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

What getHolders does on Agentek Eth

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

This tool retrieves publicly available blockchain data (holder information for a cryptocurrency token). It performs a query operation without creating, modifying, deleting, or executing any code. The blast radius of misuse is minimal—an attacker could enumerate token holders but cannot execute transactions, modify balances, or access private data. This is a classic Read category tool.

From the tool's definition Tool name and description indicate 'Fetch the list of holders' — a data retrieval operation with no modification or side effects. The verb 'Fetch' combined with 'list' and 'ordered by' confirms this is a read-only query operation.

Questions about getHolders

What does the getHolders tool do? +

Fetch the list of holders for a given ZAMM coin, ordered by balance descending. 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 getHolders? +

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

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

Can I rate-limit getHolders? +

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

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

getHolders 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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Agentek Eth's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.