Get holders of an ERC20 token.
AI agents call seitrace_get_erc20_token_holders to retrieve information from SEI MCP Server V2 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves information about token holders from the blockchain, which is a read-only operation with no side effects. It does not modify data, execute code, delete information, or move funds. Public blockchain holder data is typically non-sensitive and publicly accessible on-chain.
From the tool's definition Tool name 'seitrace_get_erc20_token_holders' and description 'Get holders of an ERC20 token' indicate a query operation that retrieves public blockchain data without modifying state or executing transactions.
Attacks that exploit this kind of access
Get holders of an ERC20 token. It is categorised as a Read tool in the SEI MCP Server V2 MCP Server, which means it retrieves data without modifying state.
Register the SEI MCP Server V2 MCP server in PolicyLayer and add a rule for seitrace_get_erc20_token_holders: 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 SEI MCP Server V2. Nothing to install.
seitrace_get_erc20_token_holders 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 seitrace_get_erc20_token_holders 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 seitrace_get_erc20_token_holders. 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.
seitrace_get_erc20_token_holders is provided by the SEI MCP Server V2 MCP server (testinguser1111111/sei-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →