refresh_taxonomy_snapshots

SERVERUnClick SOURCE@unclick/mcp-server

Medium RISK CLASS

Category Write

Parameters 40 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/refresh-taxonomy-snapshots.md

WHAT IT DOES

What refresh_taxonomy_snapshots does on UnClick

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.

RISK

Why refresh_taxonomy_snapshots is rated Medium

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

RECOMMENDED RULE

The rule that runs refresh_taxonomy_snapshots 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 refresh_taxonomy_snapshots, this is the rule to start with:

refresh_taxonomy_snapshots Rate-limited

refresh_taxonomy_snapshots 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": {
    "refresh_taxonomy_snapshots": {
      "limits": [
        {
          "counter": "refresh_taxonomy_snapshots_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 refresh_taxonomy_snapshots call is checked against it from then on.

FAQ

Questions about refresh_taxonomy_snapshots

What does the refresh_taxonomy_snapshots tool do? +

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.

What parameters does refresh_taxonomy_snapshots accept? +

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.

How do I enforce a policy on refresh_taxonomy_snapshots? +

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.

What risk level is refresh_taxonomy_snapshots? +

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

Can I rate-limit refresh_taxonomy_snapshots? +

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.

How do I block refresh_taxonomy_snapshots completely? +

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.

What MCP server provides refresh_taxonomy_snapshots? +

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.

KEEP EXPLORING

More on UnClick, and thousands of servers like it.

This server

All 1662 UnClick tools →

Across the catalogue

The MCP Attack Database →

Guides

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