Run an arbitrary IOTA CLI command. Use for operations not covered by other tools.
AI agents invoke iota_cli 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.
This tool enables execution of arbitrary CLI commands against the IOTA blockchain, which can have unpredictable and severe consequences depending on agent reasoning. While the server description mentions 'human-in-the-loop security,' the tool itself provides unrestricted command execution.
From the tool's definition Tool description states: 'Run an arbitrary IOTA CLI command.' The word 'arbitrary' combined with CLI execution capability means this tool can invoke any command-line operation supported by the IOTA CLI without restriction.
Documented attack patterns abuse exactly the kind of access iota_cli 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_cli:
{
"version": "1",
"default": "deny",
"tools": {
"iota_cli": {
"limits": [
{
"counter": "iota_cli_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}iota_cli 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.
Free to start. No card required.
Run an arbitrary IOTA CLI command. Use for operations not covered by other tools. 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.
Register the Iota Agent MCP server in PolicyLayer and add a rule for iota_cli: 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.
iota_cli 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 iota_cli 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 iota_cli. 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.
iota_cli 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.
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.