AI agents call iota_transaction to retrieve information from Iota Agent without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves transaction metadata from the blockchain using a digest identifier. Fetching is a non-destructive, side-effect-free read operation. No data is created, modified, deleted, or financial value is transferred. The 'human-in-the-loop security model' mentioned in the server description further mitigates risk for any tool that merely queries existing state.
From the tool's definition Tool name is 'iota_transaction' and description states 'Fetch transaction details by digest' — a clear read operation that queries transaction information without modification.
Documented attack patterns abuse exactly the kind of access iota_transaction 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_transaction:
{
"version": "1",
"default": "deny",
"tools": {
"iota_transaction": {}
}
}iota_transaction is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Fetch transaction details by digest. It is categorised as a Read tool in the Iota Agent MCP Server, which means it retrieves data without modifying state.
Register the Iota Agent MCP server in PolicyLayer and add a rule for iota_transaction: 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_transaction is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the iota_transaction 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_transaction. 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_transaction 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.