This record as markdown: /tools/nanidao-agentek/getwnscontenthash.md
What getWNSContenthash does on Agentek Eth
AI agents call getWNSContenthash 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 getWNSContenthash is rated Low
This tool retrieves metadata (a contenthash) associated with a .wei name record on the Ethereum Name Service. The operation is read-only, has no side effects, and does not create, modify, delete, or execute code. It is a simple data lookup operation.
From the tool's definition Tool name 'getWNSContenthash' and description 'Get the contenthash for a .wei name' indicate a retrieval operation with the verb 'Get', which queries data without modifying or executing anything.
Attacks that exploit this kind of access
The rule that runs getWNSContenthash 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 getWNSContenthash, this is the rule to start with:
getWNSContenthash 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 getWNSContenthash call is checked against it from then on.
Questions about getWNSContenthash
Get the contenthash for a .wei name. 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 getWNSContenthash: 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.
getWNSContenthash 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 getWNSContenthash 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 getWNSContenthash. 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.
getWNSContenthash 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