Saves or updates a standing rule or identity entry that loads at the start of every future session. Use whenever the user states or updates something about themselves or how they want every session to behave: 'my name', 'my role', 'I am', 'I work at', 'my preferences', 'I always', 'from now on', ...
AI agents use save_identity 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 |
|---|---|---|---|
key | string | Yes | Unique key within category (e.g. 'timezone', 'preferred_stack') |
value | string | Yes | The value to store (plain text or JSON string) |
category | string | Yes | Category: identity, preference, client, workflow, technical, standing_rule |
priority | number | — | Priority for loading order (higher = loaded first) |
Parameters from the server's own tool schema.
This tool creates or modifies persistent user profile data (identity rules, preferences, standing rules) that persists across sessions. It is reversible (can be updated/overwritten later) and has no financial, destructive, or code-execution component.
From the tool's definition Tool name 'save_identity' and description 'Saves or updates a standing rule or identity entry that loads at the start of every future session.' The verb 'Saves or updates' indicates data modification.
Attacks that exploit this kind of access
Saves or updates a standing rule or identity entry that loads at the start of every future session. Use whenever the user states or updates something about themselves or how they want every session to behave: 'my name', 'my role', 'I am', 'I work at', 'my preferences', 'I always', 'from now on', 'always remember', 'my timezone', 'my stack', 'my workflow', 'call me', or any other standing rule or identity anchor. Unlike save_fact (session-scoped context), save_identity is for rules and identity that should govern every future session. Do NOT trigger for one-time facts about a specific task or project (use save_fact instead). Do NOT trigger for information the user explicitly says is temporary. 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_identity accepts 4 parameters: key, value, category, priority. Required: key, value, category. 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_identity: 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_identity 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_identity 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_identity. 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_identity 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 →