# remove_animation_track

Remove track from animation.

Agent View of the PolicyLayer registry record for `remove_animation_track`. HTML page: https://policylayer.com/tools/yanhuifair-godot-mcp/remove-animation-track

## Facts

- Tool: `remove_animation_track`
- Server: Godot (`@yanhuifair/godot-mcp`) — https://policylayer.com/tools/yanhuifair-godot-mcp.md
- Install: `npx -y @yanhuifair/godot-mcp`
- Homepage: git+https://github.com/yanhuifair/Godot-MCP.git
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 3 (3 required)
- Recommended policy verdict: Hidden

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `scene_path` | string | yes | Path to .tscn scene file |
| `track_index` | number | yes | Track index to remove (0-based) |
| `animation_name` | string | yes | Animation name |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "remove_animation_track",
    "arguments": {
      "scene_path": "<scene_path>",
      "track_index": 0,
      "animation_name": "<animation_name>"
    }
  }
}
```

## Why remove_animation_track is rated Critical

This tool permanently deletes an animation track from a Godot animation resource. Deletion of animation data is irreversible and cannot be undone programmatically by the tool itself, fitting the Destructive category. While the severity is not critical (it affects only animation assets, not core systems), it is high because an AI agent misusing this could destroy animation work.

From the tool's own definition: "remove_animation_track: Remove track from animation. The verb 'remove' indicates deletion/removal of animation track data, which is irreversible without undo/external recovery."

## Use case

AI agents call remove_animation_track to permanently remove resources in Godot, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

## Recommended policy (PolicyLayer)

Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Godot:

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_animation_track"
  ]
}
```

## Other tools on Godot (281)

- `delete_file` — Destructive — https://policylayer.com/tools/yanhuifair-godot-mcp/delete-file.md
- `editor_delete_asset` — Destructive — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-delete-asset.md
- `editor_delete_selected` — Destructive — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-delete-selected.md
- `editor_remove_autoload` — Destructive — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-remove-autoload.md
- `editor_remove_input_action` — Destructive — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-remove-input-action.md
- `editor_remove_node` — Destructive — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-remove-node.md
- `remove_audio_bus` — Destructive — https://policylayer.com/tools/yanhuifair-godot-mcp/remove-audio-bus.md
- `remove_autoload` — Destructive — https://policylayer.com/tools/yanhuifair-godot-mcp/remove-autoload.md
- `remove_input_action` — Destructive — https://policylayer.com/tools/yanhuifair-godot-mcp/remove-input-action.md
- `remove_node` — Destructive — https://policylayer.com/tools/yanhuifair-godot-mcp/remove-node.md
- `remove_shader_graph_node` — Destructive — https://policylayer.com/tools/yanhuifair-godot-mcp/remove-shader-graph-node.md
- `compile_shader` — Execute — https://policylayer.com/tools/yanhuifair-godot-mcp/compile-shader.md
- `editor_bake_lightmaps` — Execute — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-bake-lightmaps.md
- `editor_bake_navigation` — Execute — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-bake-navigation.md
- `editor_debug_break` — Execute — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-debug-break.md
- `editor_debug_continue` — Execute — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-debug-continue.md
- `editor_debug_step` — Execute — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-debug-step.md
- `editor_debug_step_over` — Execute — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-debug-step-over.md
- `editor_enable_plugin` — Execute — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-enable-plugin.md
- `editor_evaluate_expression` — Execute — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-evaluate-expression.md
- `editor_focus` — Execute — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-focus.md
- `editor_get_class_doc` — Execute — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-get-class-doc.md
- `editor_open_asset` — Execute — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-open-asset.md
- `editor_open_dock` — Execute — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-open-dock.md
- `editor_play` — Execute — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-play.md
- `editor_reimport_asset` — Execute — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-reimport-asset.md
- `editor_reload_scene` — Execute — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-reload-scene.md
- `editor_run_gdscript` — Execute — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-run-gdscript.md
- `editor_run_specific_scene` — Execute — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-run-specific-scene.md
- `editor_set_selection` — Execute — https://policylayer.com/tools/yanhuifair-godot-mcp/editor-set-selection.md
- …and 251 more: https://policylayer.com/tools/yanhuifair-godot-mcp.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=yanhuifair-godot-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/yanhuifair-godot-mcp