List all animations in an AnimationPlayer node.
AI agents call list_animations to retrieve information from Godot MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about animations within a Godot AnimationPlayer node. It performs no side effects, does not modify game state, does not execute code, and does not delete or move data. It is purely informational, similar to a listing or search operation. The low severity reflects that unauthorized listing of animations poses minimal risk—it is discovery rather than action.
From the tool's definition Tool name 'list_animations' and description 'List all animations in an AnimationPlayer node' indicate a query/retrieval operation with no modification or execution of game logic.
Attacks that exploit this kind of access
List all animations in an AnimationPlayer node. It is categorised as a Read tool in the Godot MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Godot MCP Server MCP server in PolicyLayer and add a rule for list_animations: 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 Godot MCP Server. Nothing to install.
list_animations 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 list_animations 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 list_animations. 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.
list_animations is provided by the Godot MCP Server MCP server (neondeex/godotmcp-pro-free-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →