get_undo_history

What get_undo_history does on Mcp Godot Desenvolvimento

AI agents call get_undo_history to retrieve information from Mcp Godot Desenvolvimento without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_undo_history is rated Low

The tool retrieves historical information about undo-able actions in the Godot editor. It is a pure query operation with no side effects: it does not modify data, execute code, delete anything, or affect financial state. Belongs firmly in the Read category, with low severity since exposing undo history to an AI agent poses minimal risk—it cannot be weaponized to cause harm without additional write/execute tools.

From the tool's definition 'Lista o historico de acoes que podem ser desfeitas' (Lists the history of actions that can be undone) — this is a read-only operation that queries undo/redo state without modifying or executing anything.

The rule that runs get_undo_history safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Godot Desenvolvimento, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_undo_history, this is the rule to start with:

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

Questions about get_undo_history