Saves one human, assistant, system, or tool turn into UnClick conversation history so Orchestrator continuity can show and search it. Tethered seats should treat this as the primary receipt path after each accepted subscription chat human turn and after each assistant reply when the client can ca...
AI agents use save_conversation_turn 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 |
|---|---|---|---|
role | string | Yes | Who produced this turn |
content | string | Yes | Turn text to save, with secrets removed |
has_code | boolean | — | True when the turn contains code worth preserving for later context |
session_id | string | Yes | Stable thread or chat session identifier |
Parameters from the server's own tool schema.
This tool creates and modifies records in a conversation history system. While reversible (typical database writes can be updated or deleted), it persists user interactions and dialogue data.
From the tool's definition Tool 'Saves one human, assistant, system, or tool turn into UnClick conversation history' — uses 'Saves' indicating creation/modification of persistent records.
Risk signalsAccepts raw HTML/template content (content)
Attacks that exploit this kind of access
Saves one human, assistant, system, or tool turn into UnClick conversation history so Orchestrator continuity can show and search it. Tethered seats should treat this as the primary receipt path after each accepted subscription chat human turn and after each assistant reply when the client can call tools. If this tool is unavailable, fail loud with UNTETHERED or use the documented API fallback instead of silently continuing. Use a stable session_id for the thread. Do not store secrets, API keys, passwords, one-time codes, or private credentials. 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.
save_conversation_turn accepts 4 parameters: role, content, has_code, session_id. Required: role, content, session_id. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for save_conversation_turn: 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.
save_conversation_turn 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 save_conversation_turn 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 save_conversation_turn. 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.
save_conversation_turn 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →