How the agent confirms intent
While the agent operation is the dialogue with the agent to reach a decision, the MetaMask pop-up is the conclusion of that conversation.
Think of it as the digital equivalent of your financial advisor explaining a strategy and then handing you the final document to sign. The signature is the deliberate, necessary confirmation that you understand and consent to the action. It can turn the agent’s recommendation into a reality with your explicit approval, providing crucial peace of mind. Especially given that an agent’s interpretation can vary wildly depending on the underlying LLM, the conversational context, and the data it has access to, it’s always good to check a wallet transaction twice before approval.
MCP servers should serve both realities
The vision of a future where agents autonomously pay other agents for services necessitates the agent-controlled model. Agents in this economy will need their own capital to operate.
However, the transaction-crafter model provides a secure bridge to that future. It can be used to safely fund an agent, or to simply execute one-off transactions for simpler operations. This flexibility is key.
From a developer’s perspective, adding this capability shouldn’t be a heavy lift. If a MCP server can already prepare and sign a transaction with a key it holds, it should be able to perform the same logic without the final signing step, returning the unsigned transaction instead. This minor change unlocks a much safer and flexible paradigm for users and can even enable more complex designs, like a dedicated “signer agent” in a multi-agent system.
Therefore, any robust MCP server designed for broad adoption should provide developers with the flexibility to build applications that can:
-
Advise and craft for secure, user-centric financial decisions.
-
Execute with delegated funds for specialized, automated, and clearly defined tasks.
We recommend pursuing this dual support to foster real innovation while protecting users.
You can learn more about building Web3 agents using Google Cloud here.
