Execute an action on a tokenized object via the Event Bus. Actions are the primary way to change object state. Examples: mint tokens, transfer ownership, redeem rewards, update status. The action_type must match a registered action type, and the object must belong to a template that allows it.
AI agents invoke dual_execute_action to trigger actions in DUAL MCP Server. 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 executes arbitrary actions on blockchain objects with real-world consequences (minting, ownership transfer, reward redemption). While not inherently destructive, the Execute category is most appropriate because: (1) it runs external operations via an Event Bus whose effects depend entirely on the supplied arguments, (2) the tool permits multiple action types including financial-adjacent operations (mint,…
From the tool's definition The tool description explicitly states it 'Execute[s] an action on a tokenized object via the Event Bus' and 'Actions are the primary way to change object state.' Examples include 'mint tokens, transfer ownership, redeem rewards, update status'—all of which…
Attacks that exploit this kind of access
Execute an action on a tokenized object via the Event Bus. Actions are the primary way to change object state. Examples: mint tokens, transfer ownership, redeem rewards, update status. The action_type must match a registered action type, and the object must belong to a template that allows it. It is categorised as a Execute tool in the DUAL MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the DUAL MCP Server MCP server in PolicyLayer and add a rule for dual_execute_action: 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 DUAL MCP Server. Nothing to install.
dual_execute_action 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 dual_execute_action 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 dual_execute_action. 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.
dual_execute_action is provided by the DUAL MCP Server MCP server (ro-ro-b/dual-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →