Generate transaction intents for registering a .wei name. Returns the commit and reveal transactions needed for the two-step registration process.
AI agents use intentRegisterWNS to commit financial operations through Agentek Eth — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Registering a .wei name (Web3 Name Service) involves on-chain transactions that commit financial resources (gas fees and likely registration fees in ETH/tokens). The tool generates real blockchain transaction intents that, when executed, would result in financial obligations. This is a financial operation as it involves committing funds for a domain registration on the Ethereum network.
From the tool's definition registering a .wei name... commit and reveal transactions needed for the two-step registration process
Documented attack patterns abuse exactly the kind of access intentRegisterWNS gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Agentek Eth, and nothing reaches the server without passing your rules. This is the rule we recommend for intentRegisterWNS:
{
"version": "1",
"default": "deny",
"tools": {
"intentRegisterWNS": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to intentRegisterWNS is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Generate transaction intents for registering a .wei name. Returns the commit and reveal transactions needed for the two-step registration process. It is categorised as a Financial tool in the Agentek Eth MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Agentek Eth MCP server in PolicyLayer and add a rule for intentRegisterWNS: 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.
intentRegisterWNS is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the intentRegisterWNS 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 intentRegisterWNS. 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.
intentRegisterWNS 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.
Start from Agentek Eth, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
165 Agentek Eth tools catalogued and risk-classified — across an index of 43,000+ MCP servers.