request.gas.maxExecutionCost to constrain an EVM signing request’s maximum execution gas cost with one amount condition. The same policy applies to requests sent through REST and SDK signing flows.
Calculation and units
The fact is a decimal digit string in the network’s native-token base units, such as wei. It supportseq, ne, lt, lte, gt and gte.
maxFeePerGas already includes the priority fee ceiling; Para does not add maxPriorityFeePerGas again. The result is a maximum based on the signed gas fields, not a prediction of the gas used or the settled charge.
The fact excludes transferred native value or tokens, provider and Para billing markups, and separately charged L1 data, operator or blob fees. It is an execution-gas ceiling, like maxExecutionFeeWei in a fee estimate, rather than a transaction’s total cost.
App-owned wallet: cap execution gas at 0.001 ETH
This Guardrail denies an EVM transaction on Base when its maximum execution gas cost exceeds"1000000000000000" wei. Equality is allowed by this rule. Replace YOUR_WALLET_ID with the wallet’s Para ID.
execution-gas-limit.json
lte condition on this fact inside an accepted Request’s allow rule. A request above that limit follows the other applicable rules or reaches user review. An overlapping allow rule can still authorize it; Requests do not impose a hard denial.
Coverage
The fact applies to EVM native and token transfers, approvals, NFT transfers, contract calls and deployments, and the outer transaction that executes a Safe. Yield approvals, deposits and withdrawals use those same signing paths; each signed transaction has its own limit. Safe payment signature collection has no outer transaction gas fields. For a readable payment evaluated astransfer_native or transfer_tokens, the Guardrail above denies collection because the gas cost is missing. A Safe’s safeTxGas, baseGas and refund fields do not establish the outer transaction’s fee ceiling.
Para evaluates the gas fields of each transaction it signs, including replacements from automatic retry, speed-up and cancel, and transactions rebuilt after approval. A higher fee quote can therefore make a previously acceptable request exceed the limit.
For Para-managed sponsored transfers, the fact comes from the final UserOperation after its gas and paymaster quote are refreshed, and is checked before the payment signature. Sponsorship’s existing per-operation service ceiling also applies.
Message signatures, Safe typed-data approvals, standalone EIP-7702 authorizations and raw signatures have no final transaction gas cost. The earlier delegation authorization in a sponsored flow is separate from its final payment signature. Generic smart-account UserOperations outside Para-managed sponsorship do not provide this fact. Non-EVM wallets do not support it.
Missing or invalid gas fields are not a calldata decode gap and do not qualify for decode-gap fallback. See Facts Para cannot read for condition outcomes.
Use the existing JSON authoring flow to validate and save the policy. Test at the limit and just above it, raise the gas limit and fee ceiling separately, and repeat with a refreshed sponsored quote or replacement transaction. This is a per-request ceiling; it does not add a daily gas budget or count fees toward spending limits.