This record as markdown: /tools/nanidao-agentek/gettokeninfo.md
What getTokenInfo does on Agentek Eth
AI agents call getTokenInfo 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 getTokenInfo is rated Low
This tool retrieves information about token contracts (metadata) without creating, modifying, deleting, or executing any operations. It is a simple data query operation analogous to a GET request. The presence of financial-adjacent sibling tools (depositWETH, compareYieldTool) on this server does not change the nature of this specific tool, which has no capability to move money or create obligations.
From the tool's definition Tool name 'getTokenInfo' and description 'Fetch metadata for a token contract' indicate a read-only retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs getTokenInfo 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 getTokenInfo, this is the rule to start with:
getTokenInfo is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Agentek Eth, apply this rule, and every getTokenInfo call is checked against it from then on.
Questions about getTokenInfo
Fetch metadata for a token 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 getTokenInfo: 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.
getTokenInfo 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 getTokenInfo 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 getTokenInfo. 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.
getTokenInfo 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.
This server
Across the catalogue