check_claudemd_drift
Detect drift between AI agent config files (CLAUDE.md, AGENTS.md, .cursorrules) and the live tool/skill/command surface: dead path references, references to non-existent MCP tools, references to missing skills/commands, oversized sections. Convenience alias for
This record as markdown: /tools/nikolai-vysotskyi-trace-mcp/check-claudemd-drift.md
What check_claudemd_drift does on Trace
AI agents call check_claudemd_drift to retrieve information from Trace without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why check_claudemd_drift is rated Low
This is a read-only introspection tool that analyzes and reports on configuration state without modifying anything. It retrieves data about config files and tool surfaces to identify discrepancies. While it could inform refactoring decisions, the tool itself only reads and reports; it does not execute code, delete data, or make changes.
From the tool's definition Tool performs detection and analysis of configuration drift by comparing config files against live tool surfaces. Verifies references exist, identifies dead paths, and scans section sizes.
Attacks that exploit this kind of access
The rule that runs check_claudemd_drift safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Trace, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_claudemd_drift, this is the rule to start with:
check_claudemd_drift is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Trace, apply this rule, and every check_claudemd_drift call is checked against it from then on.
Questions about check_claudemd_drift
Detect drift between AI agent config files (CLAUDE.md, AGENTS.md, .cursorrules) and the live tool/skill/command surface: dead path references, references to non-existent MCP tools, references to missing skills/commands, oversized sections. Convenience alias for. It is categorised as a Read tool in the Trace MCP Server, which means it retrieves data without modifying state.
Register the Trace MCP server in PolicyLayer and add a rule for check_claudemd_drift: 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 Trace. Nothing to install.
check_claudemd_drift is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the check_claudemd_drift 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 check_claudemd_drift. 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.
check_claudemd_drift is provided by the Trace MCP server (nikolai-vysotskyi/trace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Trace, and thousands of servers like it.
This server
Across the catalogue