save_session

SERVERUnClick SOURCE@unclick/mcp-server

Medium RISK CLASS

Category Write

Parameters 72 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/save-session.md

WHAT IT DOES

What save_session does on UnClick

AI agents use save_session to create or update resources in UnClick, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.

Parameter	Type	Required	Description
`topics`	array	—	Topic tags for searchability
`summary`	string	Yes	Narrative of what happened: decisions, work completed, problems solved
`platform`	string	—	Platform this session ran on
`decisions`	array	—	Key decisions made during the session
`open_loops`	array	—	Unfinished tasks or questions to carry forward
`session_id`	string	Yes	Unique session identifier (timestamp or UUID)
`duration_minutes`	number	—	Approximate session duration

Parameters from the server's own tool schema.

RISK

Why save_session is rated Medium

This tool creates or modifies session summaries in persistent storage to enable session resumption. While it creates data, the operation is reversible (summaries can be overwritten or deleted) and has no side effects on external systems, financial impact, or destructive consequences. The blast radius of misuse is low—an agent could save false/misleading summaries, but users can review or re-run sessions.

From the tool's definition Tool description states 'Saves a structured summary' and 'Include: what was accomplished, key decisions made, open loops or next steps' — core function is creating/storing session data reversibly.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs save_session safely

PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For save_session, this is the rule to start with:

save_session Rate-limited

save_session stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "save_session": {
      "limits": [
        {
          "counter": "save_session_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every save_session call is checked against it from then on.

FAQ

Questions about save_session

What does the save_session tool do? +

Saves a structured summary of the current session so the next session can resume without re-asking. Use at the end of every meaningful session -- even if the user doesn't ask: 'summary', 'wrap-up', 'end of session', 'recap', 'we're done', 'see you next time', 'close out', or whenever significant work was completed, decisions were made, or open loops exist that need carrying forward. Also trigger at natural checkpoints mid-session when a major phase completes. Include: what was accomplished, key decisions made, open loops or next steps. Do NOT trigger after trivial exchanges (single Q&A, quick lookups) with nothing worth carrying forward. Do NOT trigger if the session has already been saved with no new work done since. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does save_session accept? +

save_session accepts 7 parameters: topics, summary, platform, decisions, open_loops, session_id, duration_minutes. Required: summary, session_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on save_session? +

Register the UnClick MCP server in PolicyLayer and add a rule for save_session: 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 UnClick. Nothing to install.

What risk level is save_session? +

save_session is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit save_session? +

Yes. Add a rate_limit block to the save_session 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.

How do I block save_session completely? +

Set action: deny in the PolicyLayer policy for save_session. 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.

What MCP server provides save_session? +

save_session is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on UnClick, and thousands of servers like it.

This server

All 1662 UnClick tools →

Across the catalogue

save_snapshot on Why Did You Render → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →