dry_run_transaction

// WHEN AI AGENTS USE THIS TOOL

AI agents invoke dry_run_transaction to trigger processes or run actions in Sui. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

// WHY ENFORCE A POLICY ON DRY_RUN_TRANSACTION

dry_run_transaction can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

// RECOMMENDED POLICY

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

io-github-expertvagabond-sui-mcp-server.yaml

tools:
  dry_run_transaction:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Sui policy for all 53 tools.

// DETAILS

Tool Name dry_run_transaction

Category Execute

MCP Server Sui MCP Server

Risk Level High

// MORE SUI TOOLS

Financial request_withdraw_stake Financial transfer_objects Financial transfer_sui Write create_wallet Write import_wallet Write merge_coins Write move_call Write request_add_stake

View all 53 tools →

// RELATED READING

// FAQ

What does the dry_run_transaction tool do? +

Dry-run a transaction to preview effects without executing.. It is categorised as a Execute tool in the Sui MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on dry_run_transaction? +

Add a rule in your Intercept YAML policy under the tools section for dry_run_transaction. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Sui MCP server.

What risk level is dry_run_transaction? +

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

Can I rate-limit dry_run_transaction? +

Yes. Add a rate_limit block to the dry_run_transaction rule in your Intercept 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 dry_run_transaction completely? +

Set action: deny in the Intercept policy for dry_run_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.

What MCP server provides dry_run_transaction? +

dry_run_transaction is provided by the Sui MCP server (sui-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Sui