This record as markdown: /tools/nanidao-agentek/getdecimals.md
What getDecimals does on Agentek Eth
AI agents call getDecimals 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 getDecimals is rated Low
This is a straightforward read operation querying token metadata from the blockchain. It retrieves information (token decimals) without creating, modifying, deleting, or executing any transactions or code. The blast radius of misuse is minimal since the tool only exposes public blockchain data that is already accessible via standard RPC calls.
From the tool's definition Tool description states it 'Gets the number of decimals of an ERC20 token' — a query operation that retrieves metadata about a token contract with no side effects or state changes.
Attacks that exploit this kind of access
The rule that runs getDecimals 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 getDecimals, this is the rule to start with:
getDecimals 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 getDecimals call is checked against it from then on.
Questions about getDecimals
Gets the number of decimals of an ERC20 token. 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 getDecimals: 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.
getDecimals 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 getDecimals 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 getDecimals. 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.
getDecimals 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