Remove a state from an AnimationNodeStateMachine.
AI agents call remove_state_machine_state to permanently remove resources in Godot MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes a game development artifact (animation state) from the Godot scene. While the severity is not critical (it affects only a single animation state, not the entire game), it is destructive because deletion cannot be undone except through undo functionality, and an agent misusing this could disrupt animation logic requiring manual restoration.
From the tool's definition Tool name contains 'remove' and description states it will 'Remove a state from an AnimationNodeStateMachine'.
Attacks that exploit this kind of access
Remove a state from an AnimationNodeStateMachine. It is categorised as a Destructive tool in the Godot MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Godot MCP Server MCP server in PolicyLayer and add a rule for remove_state_machine_state: 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.
remove_state_machine_state is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_state_machine_state 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 remove_state_machine_state. 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.
remove_state_machine_state 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 →