Close the current session. Call this at the end of every conversation. Triggers final state save, audit, and quality scoring.
Risk signalsBulk/mass operation — affects multiple targets
Part of the Total Recall server.
Free to start. No card required.
AI agents use session_close to create or modify resources in Total Recall. 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_close repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Total Recall.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"session_close": {
"limits": [
{
"counter": "session_close_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Total Recall policy for all 30 tools.
These attack patterns abuse exactly the kind of access session_close gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Close the current session. Call this at the end of every conversation. Triggers final state save, audit, and quality scoring.. It is categorised as a Write tool in the Total Recall MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Total Recall MCP server in PolicyLayer and add a rule for session_close: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Total Recall. Nothing to install.
session_close 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_close rule in your PolicyLayer 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 PolicyLayer policy for session_close. 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_close is provided by the Total Recall MCP server (@avi-total-recall/total-recall). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 30 Total Recall tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.