iota_move_build

THE RISK

High Risk

Building a Move package executes compilation toolchain processes on the local system. While it doesn't directly modify blockchain state or delete data, it runs external build/compile operations whose effects depend on the package contents.

From the tool's definition Build a Move package and report compilation results

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

HOW TO CONTROL IOTA_MOVE_BUILD

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_build:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "iota_move_build": {
      "limits": [
        {
          "counter": "iota_move_build_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

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

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

More Iota Agent tools

Financial iota_wallet_sign_execute Sign and execute a transaction via the agent wallet (human-in-the-loop approval required) Execute iota_cli Run an arbitrary IOTA CLI command. Use for operations not covered by other tools. Execute iota_move_publish_unsigned Generate an unsigned publish transaction for a Move package (for agent wallet signing) Execute iota_move_test_coverage Run Move tests with coverage analysis. Returns test results and coverage summary. Write iota_wallet_approve Approve a pending signing request Write iota_wallet_reject Reject a pending signing request Write iota_wallet_switch_network Switch between mainnet, testnet, and devnet Read iota_decompile Retrieve and decompile a deployed Move module. Returns the module

All 18 Iota Agent tools →

Execute tools on other servers

Frida Game Hacking MCP remove_breakpoint Procmon request_elevation WireMCP capture_packets Pentest Ai run_probe

Go deeper

High-risk tools in Iota Agent → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the iota_move_build tool do? +

Build a Move package and report compilation results. 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_build? +

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

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

Can I rate-limit iota_move_build? +

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

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

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

GOVERN IOTA AGENT →

Free to start. No card required.

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

// WHAT IOTA_MOVE_BUILD ON IOTA AGENT DOES

// THE RISK

// HOW TO CONTROL IOTA_MOVE_BUILD

// EXPLORE