Save current session state. Call this every 3-5 tool calls to protect against UI crashes. Required: task, intent, next_steps
High parameter count (12 properties); Bulk/mass operation — affects multiple targets
Part of the Session Forge MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use session_checkpoint to create or modify resources in Session Forge. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call session_checkpoint repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Session Forge.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
session_checkpoint:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Session Forge policy for all 15 tools.
Agents calling write-class tools like session_checkpoint have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Save current session state. Call this every 3-5 tool calls to protect against UI crashes. Required: task, intent, next_steps. It is categorised as a Write tool in the Session Forge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for session_checkpoint. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Session Forge MCP server.
session_checkpoint is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the session_checkpoint 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.
Set action: deny in the Intercept policy for session_checkpoint. 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.
session_checkpoint is provided by the Session Forge MCP server (session-forge). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept