destination.gasLimit transaction field sets an execution gas limit; it is not a session authorization policy and does not create a session-wide budget.
Use the available controls to bound risk instead:
- Usage limit caps how many times an allowed function can run.
- Spending limit caps cumulative token spend.
- Timeframe bounds when a function can run.
- Cross-chain permits cap what a session can bridge with
maxAmount. - One-time use limits a session to one settlement transaction per chain.
- Restrict a session removes the wildcard intent-execution fallback.