Generate a transaction intent for setting a .wei name as the primary name.
AI agents invoke intentSetPrimaryWNS to trigger actions in Agentek Eth. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool generates and likely submits a blockchain transaction to set a primary WNS (Wei Name Service) name. It triggers an external on-chain operation. While it modifies blockchain state (Write-like), it executes a transaction on Ethereum which is an external operation with real on-chain effects.
From the tool's definition Generate a transaction intent for setting a .wei name as the primary name
Documented attack patterns abuse exactly the kind of access intentSetPrimaryWNS 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 intentSetPrimaryWNS:
{
"version": "1",
"default": "deny",
"tools": {
"intentSetPrimaryWNS": {
"limits": [
{
"counter": "intentsetprimarywns_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}intentSetPrimaryWNS stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Generate a transaction intent for setting a .wei name as the primary name. It is categorised as a Execute tool in the Agentek Eth MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Agentek Eth MCP server in PolicyLayer and add a rule for intentSetPrimaryWNS: 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.
intentSetPrimaryWNS is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the intentSetPrimaryWNS 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 intentSetPrimaryWNS. 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.
intentSetPrimaryWNS 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.