check_rename

What check_rename does on Trace

AI agents call check_rename 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_rename is rated Low

This is a pure inspection tool that validates whether a rename operation would cause naming collisions. It has no side effects—it only queries and reports information about potential conflicts. The actual rename is performed by a separate tool (apply_rename). Therefore, it falls squarely in the Read category as a safe, non-destructive analysis operation.

From the tool's definition The tool name is 'check_rename' and the description states 'Pre-rename collision detection: checks the symbol'. The word 'check' and 'pre-rename' indicate this performs analysis before any actual rename operation occurs.

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

{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_rename": {}
  }
}

Questions about check_rename