intentWriteContract
Write to any smart contract by calling a state-changing function. Builds a transaction intent that can be executed if a wallet is connected. If the ABI is not provided, it will be auto-fetched from Blockscout for verified contracts.
This record as markdown: /tools/nanidao-agentek/intentwritecontract.md
What intentWriteContract does on Agentek Eth
AI agents invoke intentWriteContract 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.
Why intentWriteContract is rated High
Executes arbitrary smart contract transactions; misuse could cause irreversible on-chain effects.
From the tool's definition Write to any smart contract by calling a state-changing function
Attacks that exploit this kind of access
The rule that runs intentWriteContract 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 intentWriteContract, this is the rule to start with:
intentWriteContract 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Agentek Eth, apply this rule, and every intentWriteContract call is checked against it from then on.
Questions about intentWriteContract
Write to any smart contract by calling a state-changing function. Builds a transaction intent that can be executed if a wallet is connected. If the ABI is not provided, it will be auto-fetched from Blockscout for verified contracts. 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 intentWriteContract: 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.
intentWriteContract 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 intentWriteContract 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 intentWriteContract. 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.
intentWriteContract 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.
Across the catalogue