Session-Based Approvals
When usingprompt policies, users must approve each tool call. Session grants reduce this friction by remembering approvals for a configurable duration.
How Sessions Work
- User approves a tool call
- Tollgate creates a session grant
- Subsequent matching requests are auto-approved
- Grant expires after the configured duration
Configuration
Basic Session
Session Options
| Option | Description | Default |
|---|---|---|
enabled | Enable session grants | false |
duration | How long grants last | 5m |
scope | What gets remembered | tool |
Duration Formats
Scope Options
tool (Default)
Approves future calls to the same tool:write_file once, all future write_file calls are auto-approved.
arguments
Approves future calls with the same tool AND arguments:write_file("src/main.ts") only auto-approves future writes to src/main.ts.
server
Approves all tools on the same server:User Experience
When prompted, users see session options:Example Configurations
Interactive Development
Allow quick approvals during active work:Strict Production
Short sessions with argument-level scope:No Sessions
Every call requires explicit approval:Session Storage
Sessions are stored in the Tollgate audit database (~/.dotset/tollgate.db). They persist across restarts within their duration.
Revoking Sessions
To clear all session grants:tollgate sessions clear command.