AI agents use iota_wallet_reject to create or update resources in Iota Agent — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Iota Agent environment.
This tool modifies the state of a pending signing request by rejecting it. Since rejection transitions the request to a 'rejected' state rather than irreversibly deleting it or executing a financial transaction, it qualifies as Write (reversible data modification).
From the tool's definition Tool name 'iota_wallet_reject' and description 'Reject a pending signing request' indicate modification of a pending transaction's state by rejecting it, which is a reversible operation that modifies (transitions) the status of a signing request without…
Documented attack patterns abuse exactly the kind of access iota_wallet_reject 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_reject:
{
"version": "1",
"default": "deny",
"tools": {
"iota_wallet_reject": {
"limits": [
{
"counter": "iota_wallet_reject_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}iota_wallet_reject stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Reject a pending signing request. It is categorised as a Write tool in the Iota Agent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Iota Agent MCP server in PolicyLayer and add a rule for iota_wallet_reject: 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_wallet_reject is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the iota_wallet_reject 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_wallet_reject. 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_wallet_reject 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.