High Risk →

iota_move_publish_unsigned

Generate an unsigned publish transaction for a Move package (for agent wallet signing)

How to control iota_move_publish_unsigned ↓

AI agents invoke iota_move_publish_unsigned to trigger actions in Iota Agent. 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.

High Risk

This tool generates a publish transaction for a Move smart contract package on the IOTA blockchain. While the transaction is 'unsigned', it triggers external blockchain operations once signed and submitted — deploying smart contract code on-chain.

From the tool's definition Generate an unsigned publish transaction for a Move package (for agent wallet signing)

Documented attack patterns abuse exactly the kind of access iota_move_publish_unsigned 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_move_publish_unsigned:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "iota_move_publish_unsigned": {
      "limits": [
        {
          "counter": "iota_move_publish_unsigned_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

iota_move_publish_unsigned 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.

  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.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the iota_move_publish_unsigned tool do? +

Generate an unsigned publish transaction for a Move package (for agent wallet signing). It is categorised as a Execute tool in the Iota Agent MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on iota_move_publish_unsigned? +

Register the Iota Agent MCP server in PolicyLayer and add a rule for iota_move_publish_unsigned: 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_move_publish_unsigned? +

iota_move_publish_unsigned is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit iota_move_publish_unsigned? +

Yes. Add a rate_limit block to the iota_move_publish_unsigned 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_move_publish_unsigned completely? +

Set action: deny in the PolicyLayer policy for iota_move_publish_unsigned. 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_move_publish_unsigned? +

iota_move_publish_unsigned 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.