Wrap native ETH into WETH (Wrapped ETH) by depositing into the WETH contract. You receive an equal amount of WETH, an ERC20 token.
AI agents use depositWETH to commit financial operations through Agentek Eth — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool moves cryptocurrency assets by converting native ETH to WETH tokens. Converting crypto assets, even in equal amounts, constitutes a financial transaction that locks funds into a specific token form and potentially exposes them to smart contract risks. Any misuse—such as depositing to a compromised WETH contract or in incorrect amounts—could result in loss of user funds.
From the tool's definition The tool performs a cryptocurrency deposit operation ('Wrap native ETH into WETH by depositing into the WETH contract'), which converts one asset (ETH) into another (WETH).
Documented attack patterns abuse exactly the kind of access depositWETH 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 depositWETH:
{
"version": "1",
"default": "deny",
"tools": {
"depositWETH": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to depositWETH is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Wrap native ETH into WETH (Wrapped ETH) by depositing into the WETH contract. You receive an equal amount of WETH, an ERC20 token. 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 depositWETH: 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.
depositWETH 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 depositWETH 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 depositWETH. 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.
depositWETH 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.