@rhinestone/sdk 2.16.1 does not expose a declarative session-key policy that caps cumulative gas use. The 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.
- Restrict a session removes the wildcard intent-execution fallback.