Builds source-linked Memory Library taxonomy snapshots from active facts and sessions. Defaults to a dry run so workers can inspect planned snapshots before anything is written. Only pass dry_run=false after the dry-run output is safe and the job needs live write proof.
AI agents use refresh_taxonomy_snapshots 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 |
|---|---|---|---|
dry_run | boolean | — | When true, preview snapshot output without writing Library docs. |
max_sources | number | — | Maximum facts or sessions to scan. |
max_snapshots | number | — | Maximum taxonomy snapshots to build. |
max_sources_per_snapshot | number | — | Maximum source pointers per snapshot. |
Parameters from the server's own tool schema.
The tool writes taxonomy snapshots to a Memory Library when dry_run=false. It creates/updates persistent data structures (snapshots) derived from active facts and sessions. The dry_run default reduces risk, but the live mode performs a write operation. Not destructive as it builds/creates rather than deletes, and not execute as it's a structured data write rather than arbitrary code execution.
From the tool's definition Builds source-linked Memory Library taxonomy snapshots from active facts and sessions... Only pass dry_run=false after the dry-run output is safe and the job needs live write proof.
Attacks that exploit this kind of access
Builds source-linked Memory Library taxonomy snapshots from active facts and sessions. Defaults to a dry run so workers can inspect planned snapshots before anything is written. Only pass dry_run=false after the dry-run output is safe and the job needs live write proof. 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.
refresh_taxonomy_snapshots accepts 4 parameters: dry_run, max_sources, max_snapshots, max_sources_per_snapshot. 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 refresh_taxonomy_snapshots: 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.
refresh_taxonomy_snapshots 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 refresh_taxonomy_snapshots 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 refresh_taxonomy_snapshots. 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.
refresh_taxonomy_snapshots 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 →