Critical Risk →

iota_wallet_sign_execute

Sign and execute a transaction via the agent wallet (human-in-the-loop approval required)

How to control iota_wallet_sign_execute ↓

AI agents use iota_wallet_sign_execute to commit financial operations through Iota Agent — usually the final step of a payment, billing, or trading workflow. A call moves real money.

Critical Risk

This tool signs and executes blockchain transactions on the IOTA network. Blockchain transactions can move funds/tokens irreversibly, making this Financial in nature. Even with human-in-the-loop approval, misuse could result in unauthorized fund transfers, irreversible asset movements, or execution of malicious smart contract calls.

From the tool's definition Sign and execute a transaction via the agent wallet

Documented attack patterns abuse exactly the kind of access iota_wallet_sign_execute gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Iota Agent, and nothing reaches the server without passing your rules. This is the rule we recommend for iota_wallet_sign_execute:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "iota_wallet_sign_execute": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

Any call to iota_wallet_sign_execute is blocked until a human approves it. The rest of the server keeps working.

  1. Create a free account and register Iota Agent — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
GATE THIS TOOL →

Free to start. No card required.

Go deeper

What does the iota_wallet_sign_execute tool do? +

Sign and execute a transaction via the agent wallet (human-in-the-loop approval required). It is categorised as a Financial tool in the Iota Agent MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on iota_wallet_sign_execute? +

Register the Iota Agent MCP server in PolicyLayer and add a rule for iota_wallet_sign_execute: 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 Iota Agent. Nothing to install.

What risk level is iota_wallet_sign_execute? +

iota_wallet_sign_execute is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit iota_wallet_sign_execute? +

Yes. Add a rate_limit block to the iota_wallet_sign_execute 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.

How do I block iota_wallet_sign_execute completely? +

Set action: deny in the PolicyLayer policy for iota_wallet_sign_execute. 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.

What MCP server provides iota_wallet_sign_execute? +

iota_wallet_sign_execute is provided by the Iota Agent MCP server (scottcjn/iota-agent-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Iota Agent tool call.

Deterministic rules across all 18 Iota Agent tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

18 Iota Agent tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.