# Tool renames silently break agent skills and allowlists

Tool names change without aliases, so check the live list daily without a model.

By Ki Moon · 2026-10-05 · technique · current
Canonical: https://kihmoon.com/bench-notes/p/platform-under-you-drifts/

**Symptom:** A skill or agent prompt names a tool its MCP server no longer lists, and the step is skipped without an error.

When a tool server renames its tools with no aliases, each rename leaves skills, permission allowlists and a live agent's prompt teaching names that no longer exist, and the breakage is silent.

A daily check with no model now compares each server's live tool list with yesterday's snapshot and every hard-coded name. It stays quiet when healthy and alerts on three things:

- A server dropped a name since yesterday.
- A new stale reference appeared on a running surface.
- A weekly probe can't load a referenced connector tool.

The Model Context Protocol specification defines a tools/list request that returns a server's current tool names, and an optional list-changed notification when that list changes.

Anthropic's platform moves too, so a second daily watcher reads only Anthropic's release notes and docs. Scripts drop items that share no vocabulary with what I run, and a small model labels the rest. Rewording is never a finding.

Each change is matched against three short registers I keep by hand:

- Workarounds, each naming the upstream change that would retire it.
- Deliberate deviations, each with what would make me revisit it.
- Pain points, which outrank everything else.

The watcher proposes only. Each finding is evidence plus a ready patch or manual steps, a person applies it, and a rejection is appended to the register so the next run learns the no.

## Check your setup (read-only)

List every tool name hard-coded in your skill files, prompt files and tool allowlists. Compare the list with the tool list each MCP server reports today. If a read-only session can't query a server, use the tool list the session already shows for the server. Any hard-coded name missing from its server's list is a gap.

**Passes if:** Every hard-coded tool name appears in the current tool list of the server it names.

**Access needed:** local-config

## If it fails (changes to make later, not part of the check)

1. Collect every tool name hard-coded in skills, prompts, allowlists, routines and agent instructions into one list.
2. Compare that list and yesterday's snapshot with each MCP server's live tool list each day, with no model.
3. Alert only on a dropped name, a new stale reference on a running surface, or a failed weekly probe.
4. Keep registers of workarounds, deliberate deviations and pain points. Match each upstream release note against the registers.
5. Raise a finding against a deviation only if the change breaks that deviation's stated assumption.

**Applies if:** Your skill, prompt or allowlist files name tools from MCP servers or platforms that another party maintains.

**Skip if:** Your MCP config pins every server to a fixed version that you upgrade by hand.

Tags: drift, agents, deterministic
